[
http://jira.codehaus.org/browse/MNG-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162737#action_162737
]
Benjamin Bentmann commented on MNG-3853:
----------------------------------------
This is partly fixed in
[r738128|http://svn.eu.apache.org/viewvc?view=rev&revision=738128]. Partly
means it will only work if the profile is defined in the POM currently build.
The more general issue MNG-4009 still prevents usage of distribution management
(and any other model stuff) within a profile that is defined in a parent POM.
> [regression] Distribution Management injected by profile is not reflected by
> MavenProject
> -----------------------------------------------------------------------------------------
>
> Key: MNG-3853
> URL: http://jira.codehaus.org/browse/MNG-3853
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories, Profiles
> Affects Versions: 3.0-alpha-1
> Reporter: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> The cause of the user reported issue [Tycho: problem with
> distributionManagement in
> profile|http://www.nabble.com/Tycho%3A-problem-with-distributionManagement-in-profile-to20490017.html]
> is that the aritfact repos are created in the constructor of
> {{MavenProject}} but the the profiles are injected in a later step.
> There is other setup code in the constructor which most likely is also
> affected.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
