Try the other http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#mavenExecutorIdrather that the value you are currently using (there are two values `forked-path` and `invoker`) it may be that a parent pom is setting it different from the default... in any case it is something to try
On 14 May 2013 09:37, José Manuel Castroagudín Silva < [email protected]> wrote: > @Graham: If you remember anything you may have changed, or any tweaking to > this plugin, I'll be very interested in knowing about it. > > @Stephen : That's my "backup plan". However, I don't have permissions to > change anything on that machine, and any change would have to be requested > to a different team. This would take some time (bureaucracy can sometimes > be quite slow, hehe). As I'm just doing some tests, I would rather try > different approaches. > > well, thank you all. Any tip is welcome. > > > 2013/5/14 José Manuel Castroagudín Silva <[email protected]> > > > This is what I'm seeing: > > > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare (default-cli) > on project <project>: Failed to invoke Maven build. Error configuring > command-line. Reason: Maven executable not found at: <maven.home>/bin/mvn > -> [Help 1] > > > > (some specific details edited out) > > > > I was assuming that was the default behavior (as seen on > > http://jira.codehaus.org/browse/MRELEASE-428 ). > > > > > > > > 2013/5/14 Graham Leggett <[email protected]> > > > >> On 14 May 2013, at 08:31, José Manuel Castroagudín Silva < > >> [email protected]> wrote: > >> > >> > I've started doing some testing about maven-release plugin, and > >> everything > >> > went fine until the moment of trying it in our existing CI platform. > Due > >> > to, I think, "historical reasons", the maven executable is in this > >> machine > >> > named 'mvn3' and not 'mvn'. > >> > > >> > I've been looking around, and as for now, I would say there's no way > of > >> > telling the release plugin which executable to use. Is this so? > >> > >> Can you confirm what problem you are seeing? > >> > >> In theory, the release plugin shouldn't need to care what the name of > the > >> executable is. In our ci environment maven is also called mvn3, and it > just > >> works. > >> > >> Regards, > >> Graham > >> -- > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > > -- > > Saúde, > > > > J. M. Castroagudín > > > > > > -- > Saúde, > > J. M. Castroagudín >
