You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arnaud Heritier (JIRA)" <ji...@codehaus.org> on 2011/12/21 22:08:02 UTC
[jira] (MRELEASE-724) Release plugin doesn't honor profiles defined
in user settings
Arnaud Heritier created MRELEASE-724:
----------------------------------------
Summary: Release plugin doesn't honor profiles defined in user settings
Key: MRELEASE-724
URL: https://jira.codehaus.org/browse/MRELEASE-724
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.2.2
Reporter: Arnaud Heritier
Priority: Critical
We tried to upgrade the release plugin from 2.2.1 to 2.2.2 and it broke our release.
We don't define repositories (especially private ones) in our pom but in our developers settings (activated from command line or more often in activeProfiles)
Releasing this project fails with :
{code}
arnaud@mbp-arnaud:~/Code/eXo/cloud-management (git:develop %)$ mvn release:prepare -DdryRun=true
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
...
[INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ cloud-management-parent ---
[INFO] Resuming release from phase 'run-preparation-goals'
[INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones
[INFO] Executing goals 'clean verify'...
[WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
[INFO] [INFO] Scanning for projects...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Reactor Build Order:
...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Building eXo Cloud Management :: Parent 1.1-M4-SNAPSHOT
[INFO] [INFO] ------------------------------------------------------------------------
...
[INFO] [INFO] --- maven-license-plugin:1.9.0:check (check-headers) @ cloud-management-parent ---
[INFO] [WARNING] The POM for org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 is missing, no dependency information available
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
[INFO] [INFO] eXo Cloud Management :: Parent .................... FAILURE [1.257s]
...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [WARNING] The requested profile "exo-central" could not be activated because it does not exist.
[INFO] [WARNING] The requested profile "local-properties" could not be activated because it does not exist.
[INFO] [WARNING] The requested profile "exo-private" could not be activated because it does not exist.
[INFO] [WARNING] The requested profile "exo-staging" could not be activated because it does not exist.
[INFO] [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check (check-headers) on project cloud-management-parent: Execution check-headers of goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check failed: Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its dependencies could not be resolved: Failure to find org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 in http://repository.exoplatform.org/public was cached in the local repository, resolution will not be reattempted until the update interval of exo-fr-mirror has elapsed or updates are forced -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] eXo Cloud Management :: Parent .................... FAILURE [5.210s]
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
...
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project cloud-management-parent: Maven execution failed, exit code: '1' -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{code}
The build is failing in the {{maven-license-plugin}} which requires a private dependency {{org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1}} which isn't found as the profile {{exo-private}} is omitted.
It is a regression in 2.2.2 as it worked with all previous versions. Downgrading to 2.2.1 solved the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-724) Release plugin doesn't honor profiles defined
in user settings
Posted by "Eric Chatellier (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287838#comment-287838 ]
Eric Chatellier commented on MRELEASE-724:
------------------------------------------
Same error here.
> Release plugin doesn't honor profiles defined in user settings
> --------------------------------------------------------------
>
> Key: MRELEASE-724
> URL: https://jira.codehaus.org/browse/MRELEASE-724
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: MRELEASE-724.log
>
>
> We tried to upgrade the release plugin from 2.2.1 to 2.2.2 and it broke our release.
> We don't define repositories (especially private ones) in our pom but in our developers settings (activated from command line or more often in activeProfiles)
> Releasing this project fails with :
> {code}
> arnaud@mbp-arnaud:~/Code/eXo/cloud-management (git:develop %)$ mvn release:prepare -DdryRun=true
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> ...
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ cloud-management-parent ---
> [INFO] Resuming release from phase 'run-preparation-goals'
> [INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Build Order:
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building eXo Cloud Management :: Parent 1.1-M4-SNAPSHOT
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] --- maven-license-plugin:1.9.0:check (check-headers) @ cloud-management-parent ---
> [INFO] [WARNING] The POM for org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 is missing, no dependency information available
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Summary:
> [INFO] [INFO]
> [INFO] [INFO] eXo Cloud Management :: Parent .................... FAILURE [1.257s]
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "exo-central" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "local-properties" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-private" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-staging" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check (check-headers) on project cloud-management-parent: Execution check-headers of goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check failed: Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its dependencies could not be resolved: Failure to find org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 in http://repository.exoplatform.org/public was cached in the local repository, resolution will not be reattempted until the update interval of exo-fr-mirror has elapsed or updates are forced -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] eXo Cloud Management :: Parent .................... FAILURE [5.210s]
> ...
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project cloud-management-parent: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> The build is failing in the {{maven-license-plugin}} which requires a private dependency {{org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1}} which isn't found as the profile {{exo-private}} is omitted.
> It is a regression in 2.2.2 as it worked with all previous versions. Downgrading to 2.2.1 solved the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-724) Release plugin doesn't honor profiles defined
in user settings
Posted by "Patrick Decat (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286553#comment-286553 ]
Patrick Decat commented on MRELEASE-724:
----------------------------------------
Got the same behaviour, but with the perform goal.
Downgrading fixed it.
> Release plugin doesn't honor profiles defined in user settings
> --------------------------------------------------------------
>
> Key: MRELEASE-724
> URL: https://jira.codehaus.org/browse/MRELEASE-724
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: MRELEASE-724.log
>
>
> We tried to upgrade the release plugin from 2.2.1 to 2.2.2 and it broke our release.
> We don't define repositories (especially private ones) in our pom but in our developers settings (activated from command line or more often in activeProfiles)
> Releasing this project fails with :
> {code}
> arnaud@mbp-arnaud:~/Code/eXo/cloud-management (git:develop %)$ mvn release:prepare -DdryRun=true
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> ...
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ cloud-management-parent ---
> [INFO] Resuming release from phase 'run-preparation-goals'
> [INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Build Order:
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building eXo Cloud Management :: Parent 1.1-M4-SNAPSHOT
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] --- maven-license-plugin:1.9.0:check (check-headers) @ cloud-management-parent ---
> [INFO] [WARNING] The POM for org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 is missing, no dependency information available
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Summary:
> [INFO] [INFO]
> [INFO] [INFO] eXo Cloud Management :: Parent .................... FAILURE [1.257s]
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "exo-central" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "local-properties" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-private" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-staging" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check (check-headers) on project cloud-management-parent: Execution check-headers of goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check failed: Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its dependencies could not be resolved: Failure to find org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 in http://repository.exoplatform.org/public was cached in the local repository, resolution will not be reattempted until the update interval of exo-fr-mirror has elapsed or updates are forced -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] eXo Cloud Management :: Parent .................... FAILURE [5.210s]
> ...
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project cloud-management-parent: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> The build is failing in the {{maven-license-plugin}} which requires a private dependency {{org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1}} which isn't found as the profile {{exo-private}} is omitted.
> It is a regression in 2.2.2 as it worked with all previous versions. Downgrading to 2.2.1 solved the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-724) Release plugin doesn't honor profiles defined
in user settings
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-724:
-------------------------------------
Attachment: MRELEASE-724.log
debug logs
> Release plugin doesn't honor profiles defined in user settings
> --------------------------------------------------------------
>
> Key: MRELEASE-724
> URL: https://jira.codehaus.org/browse/MRELEASE-724
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: MRELEASE-724.log
>
>
> We tried to upgrade the release plugin from 2.2.1 to 2.2.2 and it broke our release.
> We don't define repositories (especially private ones) in our pom but in our developers settings (activated from command line or more often in activeProfiles)
> Releasing this project fails with :
> {code}
> arnaud@mbp-arnaud:~/Code/eXo/cloud-management (git:develop %)$ mvn release:prepare -DdryRun=true
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> ...
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ cloud-management-parent ---
> [INFO] Resuming release from phase 'run-preparation-goals'
> [INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Build Order:
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building eXo Cloud Management :: Parent 1.1-M4-SNAPSHOT
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] --- maven-license-plugin:1.9.0:check (check-headers) @ cloud-management-parent ---
> [INFO] [WARNING] The POM for org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 is missing, no dependency information available
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Summary:
> [INFO] [INFO]
> [INFO] [INFO] eXo Cloud Management :: Parent .................... FAILURE [1.257s]
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "exo-central" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "local-properties" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-private" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-staging" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check (check-headers) on project cloud-management-parent: Execution check-headers of goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check failed: Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its dependencies could not be resolved: Failure to find org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 in http://repository.exoplatform.org/public was cached in the local repository, resolution will not be reattempted until the update interval of exo-fr-mirror has elapsed or updates are forced -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] eXo Cloud Management :: Parent .................... FAILURE [5.210s]
> ...
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project cloud-management-parent: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> The build is failing in the {{maven-license-plugin}} which requires a private dependency {{org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1}} which isn't found as the profile {{exo-private}} is omitted.
> It is a regression in 2.2.2 as it worked with all previous versions. Downgrading to 2.2.1 solved the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-724) Release plugin doesn't honor profiles defined
in user settings
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287916#comment-287916 ]
Olivier Lamy commented on MRELEASE-724:
---------------------------------------
fixed in the coming mvn 3.0.4 see MNG-5224
> Release plugin doesn't honor profiles defined in user settings
> --------------------------------------------------------------
>
> Key: MRELEASE-724
> URL: https://jira.codehaus.org/browse/MRELEASE-724
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: MRELEASE-724.log
>
>
> We tried to upgrade the release plugin from 2.2.1 to 2.2.2 and it broke our release.
> We don't define repositories (especially private ones) in our pom but in our developers settings (activated from command line or more often in activeProfiles)
> Releasing this project fails with :
> {code}
> arnaud@mbp-arnaud:~/Code/eXo/cloud-management (git:develop %)$ mvn release:prepare -DdryRun=true
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> ...
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ cloud-management-parent ---
> [INFO] Resuming release from phase 'run-preparation-goals'
> [INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Build Order:
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building eXo Cloud Management :: Parent 1.1-M4-SNAPSHOT
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] --- maven-license-plugin:1.9.0:check (check-headers) @ cloud-management-parent ---
> [INFO] [WARNING] The POM for org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 is missing, no dependency information available
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Summary:
> [INFO] [INFO]
> [INFO] [INFO] eXo Cloud Management :: Parent .................... FAILURE [1.257s]
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "exo-central" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "local-properties" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-private" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-staging" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check (check-headers) on project cloud-management-parent: Execution check-headers of goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check failed: Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its dependencies could not be resolved: Failure to find org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 in http://repository.exoplatform.org/public was cached in the local repository, resolution will not be reattempted until the update interval of exo-fr-mirror has elapsed or updates are forced -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] eXo Cloud Management :: Parent .................... FAILURE [5.210s]
> ...
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project cloud-management-parent: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> The build is failing in the {{maven-license-plugin}} which requires a private dependency {{org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1}} which isn't found as the profile {{exo-private}} is omitted.
> It is a regression in 2.2.2 as it worked with all previous versions. Downgrading to 2.2.1 solved the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-724) Release plugin doesn't honor profiles defined
in user settings
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly closed MRELEASE-724.
-------------------------------------
Resolution: Duplicate
Duplicate of MNG-5224
> Release plugin doesn't honor profiles defined in user settings
> --------------------------------------------------------------
>
> Key: MRELEASE-724
> URL: https://jira.codehaus.org/browse/MRELEASE-724
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: MRELEASE-724.log
>
>
> We tried to upgrade the release plugin from 2.2.1 to 2.2.2 and it broke our release.
> We don't define repositories (especially private ones) in our pom but in our developers settings (activated from command line or more often in activeProfiles)
> Releasing this project fails with :
> {code}
> arnaud@mbp-arnaud:~/Code/eXo/cloud-management (git:develop %)$ mvn release:prepare -DdryRun=true
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> ...
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ cloud-management-parent ---
> [INFO] Resuming release from phase 'run-preparation-goals'
> [INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Build Order:
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building eXo Cloud Management :: Parent 1.1-M4-SNAPSHOT
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] --- maven-license-plugin:1.9.0:check (check-headers) @ cloud-management-parent ---
> [INFO] [WARNING] The POM for org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 is missing, no dependency information available
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Summary:
> [INFO] [INFO]
> [INFO] [INFO] eXo Cloud Management :: Parent .................... FAILURE [1.257s]
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "exo-central" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "local-properties" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-private" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-staging" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check (check-headers) on project cloud-management-parent: Execution check-headers of goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check failed: Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its dependencies could not be resolved: Failure to find org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 in http://repository.exoplatform.org/public was cached in the local repository, resolution will not be reattempted until the update interval of exo-fr-mirror has elapsed or updates are forced -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] eXo Cloud Management :: Parent .................... FAILURE [5.210s]
> ...
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project cloud-management-parent: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> The build is failing in the {{maven-license-plugin}} which requires a private dependency {{org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1}} which isn't found as the profile {{exo-private}} is omitted.
> It is a regression in 2.2.2 as it worked with all previous versions. Downgrading to 2.2.1 solved the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-724) Release plugin doesn't honor profiles defined
in user settings
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287273#comment-287273 ]
Andrei Pozolotin commented on MRELEASE-724:
-------------------------------------------
1) same problem here;
2) I think this has to do with the following:
the inner maven invocation:
[DEBUG] Executing: /bin/sh -c cd /Users/arnaud/Code/eXo/cloud-management && /Users/arnaud/Applications/apache-maven-3.0.4-RC3/bin/mvn -X -D maven.repo.local=/Users/arnaud/.m2/repository -s /private/var/folders/t0/rlgvq9wj557dbt5zbxwg3c340000gn/T/release-settings1260821738839931094.xml -P exo-private,exo-staging,exo-central,local-properties clean verify
uses generated-on-the-fly settings.xml such as:
release-settings1260821738839931094.xml
if you intercept this file like this:
while : ; do cp release-settings*.xml release-settings.xml.tmp ; sleep 0.01 ; done
and look inside, you will see that it does not contain any profile definitions
that it should have imported from ${user.home}/.m2/settings.xml
> Release plugin doesn't honor profiles defined in user settings
> --------------------------------------------------------------
>
> Key: MRELEASE-724
> URL: https://jira.codehaus.org/browse/MRELEASE-724
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: MRELEASE-724.log
>
>
> We tried to upgrade the release plugin from 2.2.1 to 2.2.2 and it broke our release.
> We don't define repositories (especially private ones) in our pom but in our developers settings (activated from command line or more often in activeProfiles)
> Releasing this project fails with :
> {code}
> arnaud@mbp-arnaud:~/Code/eXo/cloud-management (git:develop %)$ mvn release:prepare -DdryRun=true
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> ...
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ cloud-management-parent ---
> [INFO] Resuming release from phase 'run-preparation-goals'
> [INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Build Order:
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building eXo Cloud Management :: Parent 1.1-M4-SNAPSHOT
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] --- maven-license-plugin:1.9.0:check (check-headers) @ cloud-management-parent ---
> [INFO] [WARNING] The POM for org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 is missing, no dependency information available
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Summary:
> [INFO] [INFO]
> [INFO] [INFO] eXo Cloud Management :: Parent .................... FAILURE [1.257s]
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> ...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "exo-central" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "local-properties" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-private" could not be activated because it does not exist.
> [INFO] [WARNING] The requested profile "exo-staging" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check (check-headers) on project cloud-management-parent: Execution check-headers of goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check failed: Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its dependencies could not be resolved: Failure to find org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 in http://repository.exoplatform.org/public was cached in the local repository, resolution will not be reattempted until the update interval of exo-fr-mirror has elapsed or updates are forced -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] eXo Cloud Management :: Parent .................... FAILURE [5.210s]
> ...
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project cloud-management-parent: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> The build is failing in the {{maven-license-plugin}} which requires a private dependency {{org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1}} which isn't found as the profile {{exo-private}} is omitted.
> It is a regression in 2.2.2 as it worked with all previous versions. Downgrading to 2.2.1 solved the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira