releaseProfiles has no effect without passing profiles in the command line

Just a pointer. I got caught out by this unexpectedly. It turned out that on one machine, I didn't have any profiles present in my settings.xml.

If you want to reproduce this, try temporarily moving your settings.xml out of the way.

Hi!

What remains to be done before this patch can be incorporated in the release plugin?

I just got hit by this and I'd really appreciate if this could be fixed.

Regards /Johan

I actually had to use the following to get things to work:
mvn release:perform -Darguments="-PmyProfileToActivate"

I think this is because I'm also using the -DconnectionUrl=... option and don't have any profiles defined in my settings.xml.

I ran into a comparable problem:
I´ve had a 'local' profile, which was activated by default.
At mvn release:perform I want the profile 'release' to be activated - but what happened was that both profiles ('local' and 'release') were activated, trying to set the same variable.
My solution was, to remove the 'local' profile, which was activated by default before.

but then, at mvn release:perform no more profiles got activated:
[DEBUG] Executing: cmd.exe /X /C "C:\eap\apache-maven-2.2.1\bin\mvn.bat -X -D maven.repo.local=D:\mavenrepo -f maven-release-test -D performRelease=true deploy site-deploy"

=> So i now added a 'dummy' profile that is activated by default, but does nothing:
[DEBUG] Executing: cmd.exe /X /C "C:\eap\apache-maven-2.2.1\bin\mvn.bat -X -D maven.repo.local=D:\mavenrepo -f maven-release-test -D performRelease=true -P dummy,release deploy site-deploy"

using this workaround, I got my 'release' profile to work - after spending some hours with this issue....Please, fix that in one of the next releases or give a hint in the documentation.

Thanx, Torsten

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

This is the exact same patch as before just created against the new directory layout.

All tests still pass.

Needs some integration tests that fail before the patch is applied and pass after the patch is applied to:

1. prove there is an issue

2. prove the issue is fixed

3. prevent the issue from arising again.

I know this looks like a simple fix, but we really need integration tests to apply patches or quality will just decrease

Thanks for the comment and the explanation.

If no one else jumps on it before I'll try to provide an updated patch but I can't commit to a date yet. Need to understand how ITs work here first, too.

This works fine under version 2.2.2 of the plugin. I am actively using it. I think it can be closed.

@Martin, it looks like the releaseProfiles are only passed when there's at least one other active profile, so it doesn't have to be a problem for everybody. Like Stephen already said before: first proof with an IT that this is still an issue.

fyi: this is still a problem as of 2.3.2;

hey, this soon will make it into a book of records!
it will be named: "the curse of the maven release plugin"
http://stackoverflow.com/questions/3291938/maven-release-plugin-ignores-releaseprofile

workaround is still the same: put a dummy profile in settings.xml

<profiles>
	<profile>
		<id>default</id>
	</profile>
</profiles>

<activeProfiles>
	<activeProfile>default</activeProfile>
</activeProfiles>

Fixed in r1391992

thank you!