[infinispan-issues] [JBoss JIRA] (ISPN-2252) mvn deploy -Pdistribution doesn't uploads the sources

[Adrian Nistor (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Nistor reopened ISPN-2252:
---------------------------------



The current fix has the net effect of completely disabling generation of runtime-classpath.txt for submodules (consequently, the demos from the distribution no longer work in 5.2.0.alpha4). No submodule is child of root pom. The stuff we moved to root has no effect on our submodules, so we should move it back. To get the sources jars generated we should activate the 'extras' profile manually (-Pdistribution,extras). There is no sane way to circumvent the way activeByDefault works (by design) in maven. We could though merge distribution and extras profile if they are always used together. Wdyt?
                
> mvn deploy -Pdistribution doesn't uploads the sources
> -----------------------------------------------------
>
>                 Key: ISPN-2252
>                 URL: https://issues.jboss.org/browse/ISPN-2252
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.2.0.Alpha3
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>             Fix For: 5.2.0.Alpha4
>
>
> Here's why:
> - the "distribution" which we use for releasing which was initially present in root's pom.xml was also added in "parent/pom.xml" (ISPN-1959).
> - the sources to be uploaded were generated by an "activeByDefault" profile located in "parent/pom.xml", named "extras"
> - the "activeByDefault" configuration has a rather error prone semantic, that is it only activates a profile if there's no other profile in the same file explicitly or implicitly active[1]
> - not having the source is a show stopper for releasing as nexus has a validation in place to check for sources (a good thing).
> The solution is to merge the "distribution" profile from parent\pom.xml into the preexisting one from root. This would allow the "extras" to kick in as there isn't any other active profile in parent\pom.xml (at least when running -Pdistribution).
> [1] from mvn documentation
> {quote}
> ... This profile will automatically be active for all builds unless another profile in the same POM is activated using one of the previously described methods. All profiles that are active by default are automatically deactivated when a profile in the POM is activated on the command line or through its activation config. ...
> {quote} 

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