[
https://issues.apache.org/jira/browse/MNG-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958504#comment-14958504
]
Arend v. Reinersdorff commented on MNG-5903:
--------------------------------------------
In my Javadoc use case I use the javadoc:aggregate goal. Using the skip option
in a module doesn't work.
If you have a suggestion for my particular Javadoc use case, here's the
question on Stackoverflow. I'd be grateful for any suggestions:
http://stackoverflow.com/questions/32949268/how-to-exclude-a-single-module-from-javadoc-generation-in-a-maven-multi-module-p
Please note that there are other use cases for excluding modules. For example
MNG-5230 mentions excluding slow building modules from ci-build.
> Option in profiles to exclude modules from reactor
> --------------------------------------------------
>
> Key: MNG-5903
> URL: https://issues.apache.org/jira/browse/MNG-5903
> Project: Maven
> Issue Type: New Feature
> Reporter: Arend v. Reinersdorff
>
> Sometimes it is useful to exclude modules from a reactor build.
> One reason for this can be: Don't generate Javadoc for a testing module.
> Since Maven 3.2.1 it is possible to exclude modules with command line
> options, eg. mvn -pl !integration-tests
> See MNG-5230 "Command line option to exclude modules from reactor". In this
> ticket enabling module exclusion for profiles was discussed, but apparently
> not implemented.
> I'm currently using the -pl command line option on our build server to
> exclude two projects of a multi module build from Javadoc generation. But I
> would much prefer to keep this logic in the pom.xml. Something like this:
> <profile>
> <id>javadoc</id>
> <modules>
> <module>!integration-tests</module>
> </modules>
> </profile>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)