[
https://issues.apache.org/jira/browse/MRELEASE-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077081#comment-17077081
]
Arnaud Heritier commented on MRELEASE-1038:
-------------------------------------------
[~olamy] I think we should have considered this bug as a higher priority and do
another release.
I agree that there is a workaround but the time lost to fail a release, to
identify that the problems comes from this bug may give a lot of stress to some
people.
Yes it's a M1, not a final release but in our ecosystem we have sadly often a
lot of releases in non-final versions for a long time and our users are using
them with no fear in general....
> releaseProfiles get overriden by exec.pomFileName
> -------------------------------------------------
>
> Key: MRELEASE-1038
> URL: https://issues.apache.org/jira/browse/MRELEASE-1038
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 3.0.0-M1
> Reporter: Benoit MESSAGER
> Assignee: Olivier Lamy
> Priority: Minor
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Profiles specified in <configuration>.<releaseProfiles> are overrided by the
> pom file name.
> This come from : org.apache.maven.shared.release.config.ReleaseUtils line 130
> :
> {code:java}
> if ( properties.containsKey( "exec.activateProfiles" ) )
> {
> builder.setActivateProfiles( Arrays.asList( properties.getProperty(
> "exec.pomFileName" ).split( "," ) ) );
> }
> {code}
> this look like a failed copy/paste
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
