Perhaps there is a bug on Mac. I do what you say and get this:
[INFO] [INFO] Scanning for projects...
[INFO] [WARNING]
[INFO] Profile with id: 'release' has not been activated.
[INFO]
pom.xml:
maven-release-plugin
2.0
svn://saoj-la.dyndns.org/webapp-test/tags
scm:svn:svn://
Nope.
bind the execution to the install phase in a profile and then use *
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#releaseProfilesto
activate the profile on release perform
*
On 10 August 2010 16:07, Sergio Oliveira wrote:
> Problem is NOT switching 'deploy' to 'in
Problem is NOT switching 'deploy' to 'install'. A install
will do it.
Problem IS cascading an exec:exec after release:perform. You can try and you
will see that's NOT possible. Probably something related to the fact that
release:perform forks another maven process. Even mvn release:perform
exec:ex
Have a look at *
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#releaseProfiles
*
2010/8/10 Martin Schayna
> I am using this configuration for firing goal 'install' instead of 'deploy'
> in 'release:perform':
>
>
> ...
>
>...
>
>
> maven-release-plugin
> 2.0-beta-
I am using this configuration for firing goal 'install' instead of
'deploy' in 'release:perform':
...
...
maven-release-plugin
2.0-beta-9
true
install
false
M.
On 08/10/2010 06:38 AM, Sergio Oliveira wrote:
I change goals from release:perform to install instead of the default
d
have a look at the releaseProfiles configuration parameter of
release:perform
On 10 August 2010 05:38, Sergio Oliveira wrote:
> I change goals from release:perform to install instead of the default
> deploy.
>
> But maven ignores my profile 'release' for phase 'install'. It works when I
> call m
