Posted by rrialq on Aug 12, 2019; 10:43am
URL: https://discuss.asciidoctor.org/About-Asciidoctor-Maven-integration-A-custom-lifecycle-tp7063p7067.html

In my current projects I use a profile to download a theme (with dependency:get and unpack it) , build the module with asciidoctor), zip the results and send the files to a Nexus site repository, but this is too much complicated if you want to reply this across multiple projects. This profile is in a parent pom, but this is not as effective as we need, because of using the default lifecycle.

I have developed a custom lifecycle that meets my needs, but I don't know if meet other people needs.
I will publish the code in github next days, when I finish the tests.

The new lifecycle contains its own phases, so it allows to build only the documentation, because when you want to build it you use mvn build, and this lifecycle does not overlap with the default, so I think it is a better approach than using the standard lifecycle.

Think in the site lifecycle, it also does not overlap with the standard lifecycle, and it exists to solve the problem of the site documentation.