You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Rocher Suchard (Jira)" <ji...@apache.org> on 2020/01/27 23:34: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=17024760#comment-17024760 ] 

Rocher Suchard commented on MRELEASE-1038:
------------------------------------------

The fact that the {{performRelease}} was removed and this issue is problematic: I was using the {{performRelease}} to trigger the {{maven-gpg-plugin}}.

The alternative does not work and is pretty annoying due to this message:
{code:java}
[INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
{code}

For those interested in testing maven-release-plugin 3.0.0.M1, this can be fixed like this:

{code:xml}
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-release-plugin</artifactId>
          <version>3.0.0-M1</version>
          <configuration>
            <tagNameFormat>v@{project.version}</tagNameFormat>
            <autoVersionSubmodules>true</autoVersionSubmodules>
            <!-- <releaseProfiles>release-sign-artifacts</releaseProfiles> -->
            <arguments> -Prelease-sign-artifacts </arguments>
          </configuration>
        </plugin>
{code}

However the plugin will get executed in the verify phase of the release:prepare as well.



> 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
>            Priority: Minor
>
> 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)