You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Symons (Jira)" <ji...@apache.org> on 2021/04/19 10:30:00 UTC

[jira] [Commented] (MRELEASE-1038) releaseProfiles get overriden by exec.pomFileName

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

Mark Symons commented on MRELEASE-1038:
---------------------------------------

[~olamy], with 3.0.0-M2 never having been released and 3.0.0-M4 now released and available in Maven Central, should this issue (and others with fix version 3.0.0-M2), have the fix version tweaked to 3.0.0-M4?   

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