[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283370#comment-283370 ]
Chris Watts commented on MRELEASE-459: -------------------------------------- This also seems to effect maven3 maven-release-plugin:2.2.1 Not sure if it's to do with running maven thus: mvn release:prepare release:perform > releaseProfiles has no effect without passing profiles in the command line > --------------------------------------------------------------------------- > > Key: MRELEASE-459 > URL: https://jira.codehaus.org/browse/MRELEASE-459 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform > Affects Versions: 2.0-beta-8, 2.0-beta-9 > Reporter: Andreas Christoforides > Attachments: patch.txt > > > The releaseProfiles parameter on the perform goal is not taken into > consideration when no other profiles are passed in the command line. In other > words, the current code only uses the value of the parameter if you have > additional profiles passed in. > Example: > mvn release:perform -P someProfile (uses releaseProfiles value) > mvn release:perform (does NOT use releaseProfiles value) > The plugin should use the parameter even if no other profiles are passed. It > should actually encourage release profiles configured in your POM as opposed > to arbitrary profiles passed in the command line. > I have included a patch that uses the releaseProfiles parameter regardless of > any profiles passed in the command line. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira