maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From José Manuel Castroagudín Silva <>
Subject Re: release plugin, different executable name ('mvn3')
Date Tue, 14 May 2013 10:11:03 GMT
"This seems to be a general maven problem, not a release plugin problem."

Might be. However, right now, my problem seems to be that the release
plugin is, or seems to be, trying to spawn a new 'mvn' process. And it's
trying to launch ${maven.home}/bin/mvn (which does not exist).

So I thought that maybe this specific plugin could have some parameter,
property, or any mean to be told which executable to use. It would make
sense, if it's really spawning a new maven process.

@Stephen : I'm sorry, but I don't get what should I do with that
mavenExecutorId parameter. I already had seen it before, but I couldn't
figure out how to use it. I searched for some documentation, or
configuration examples, or anything, and have just found this: [1] (which
seems not very helpful, at least for me) . As I said, I'm fairly new with
maven, and this might be something trivial for experienced users, so if
someone could point me out to some documentation on how to use that
parameter, i'd really appreciate it.

[1] ->

Thank you all,

2013/5/14 Graham Leggett <>

> On 14 May 2013, at 10:02 AM, José Manuel Castroagudín Silva <
>> wrote:
> > 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
> > ).
> While maven doesn't care about the name of the executable used to run
> maven, maven does care that MAVEN_HOME follows the correct structure, and
> it looks like MAVEN_HOME isn't correctly laid out, most specifically that
> the bin directory exists and has an "mvn" script in it.
> In our case we have packaged maven to have an out-the-box MAVEN_HOME
> structure, and then symlinked /usr/bin/mvn3 to ${MAVEN_HOME}/bin/mvn, and
> that worked for us.
> This seems to be a general maven problem, not a release plugin problem.
> Regards,
> Graham
> --
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:


J. M. Castroagudín

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message