maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5903) Option in profiles to exclude modules from reactor
Date Wed, 07 Oct 2015 07:52:26 GMT

    [ https://issues.apache.org/jira/browse/MNG-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946463#comment-14946463
] 

Michael Osipov commented on MNG-5903:
-------------------------------------

This would be clearly a breaking change because too many tools read out the {{<module>}}
element. I make this the other way around. I have enabled the module explicitly.

> 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)

Mime
View raw message