|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I've confirmed that this is still not supported with 2.8 version of maven-project, but I don't have the time to setup jenkins nightly now.
> it seems to be rather unusual (it doesn't look like many actually need this) I wouldn't consider it Major loss of functionality either.
It is a major loss of functionality for me – this was actually the reason to upgrade to maven 3.2 for me
It might be simply that not many people are aware of the functionality, but the problem is well known and used to be solved by dupicating module declarations over profiles, c.f. https://stackoverflow.com/questions/5539348/how-to-exclude-a-module-from-a-maven-reactor-build (the old answer still has more votes)