Re: release plugin, different executable name ('mvn3')
Why not just create a shell script called mvn that passes through to your mvn3? On 14 May 2013 08:31, José Manuel Castroagudín Silva chavescesu...@gmail.com wrote: Hi all, 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? Let me say that I'm in no way a maven expert, and maybe I've missed something somewhere. Maybe there's a way of setting this, and I've been just unable to find it. So, in short: is this possible? I'm afraid I cannot change the executable name on this machine, since a lot of configurations depend on it, in several languages, so I don't have the permissions to do that. Anyway, thanks in advance. -- Saúde, J. M. Castroagudín
Re: release plugin, different executable name ('mvn3')
On 14 May 2013, at 08:31, José Manuel Castroagudín Silva chavescesu...@gmail.com 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin, different executable name ('mvn3')
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 minf...@sharp.fm On 14 May 2013, at 08:31, José Manuel Castroagudín Silva chavescesu...@gmail.com 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Saúde, J. M. Castroagudín
Re: release plugin, different executable name ('mvn3')
@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 chavescesu...@gmail.com 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 minf...@sharp.fm On 14 May 2013, at 08:31, José Manuel Castroagudín Silva chavescesu...@gmail.com 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Saúde, J. M. Castroagudín -- Saúde, J. M. Castroagudín
Re: release plugin, different executable name ('mvn3')
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 chavescesu...@gmail.com 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 chavescesu...@gmail.com 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 minf...@sharp.fm On 14 May 2013, at 08:31, José Manuel Castroagudín Silva chavescesu...@gmail.com 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Saúde, J. M. Castroagudín -- Saúde, J. M. Castroagudín
Re: release plugin, different executable name ('mvn3')
On 14 May 2013, at 10:02 AM, José Manuel Castroagudín Silva
chavescesu...@gmail.com 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
http://jira.codehaus.org/browse/MRELEASE-428 ).
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin, different executable name ('mvn3')
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] -
http://maven.apache.org/maven-release/maven-release-manager/apidocs/org/apache/maven/shared/release/exec/MavenExecutor.html
Thank you all,
2013/5/14 Graham Leggett minf...@sharp.fm
On 14 May 2013, at 10:02 AM, José Manuel Castroagudín Silva
chavescesu...@gmail.com 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
http://jira.codehaus.org/browse/MRELEASE-428 ).
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Saúde,
J. M. Castroagudín
Re: release plugin, different executable name ('mvn3')
try the two valid values.
should be possible to configure it via the CLI
e.g.
mvn -DmavenExecutorId=forked-path -Ddry-run=true release:prepare
mvn -DmavenExecutorId=invoker -Ddry-run=true release:prepare
Though if the configuration for the release plugin in your pom.xml or a
parent pom.xml is setting the value you will likely need to edit the
pom.xml to change the value.
On 14 May 2013 11:11, José Manuel Castroagudín Silva
chavescesu...@gmail.com wrote:
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] -
http://maven.apache.org/maven-release/maven-release-manager/apidocs/org/apache/maven/shared/release/exec/MavenExecutor.html
Thank you all,
2013/5/14 Graham Leggett minf...@sharp.fm
On 14 May 2013, at 10:02 AM, José Manuel Castroagudín Silva
chavescesu...@gmail.com 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
http://jira.codehaus.org/browse/MRELEASE-428 ).
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Saúde,
J. M. Castroagudín
Re: release plugin, different executable name ('mvn3')
I tried -DmavenExecutorId=forked-path, resulting in a slightly different
error. That makes me think that maybe there's some aditional parameter (the
path to the executable itself) that could actually work combined with this
one.
No idea what would this parameter be, though, hehe.
Thanks again,
2013/5/14 Stephen Connolly stephen.alan.conno...@gmail.com
try the two valid values.
should be possible to configure it via the CLI
e.g.
mvn -DmavenExecutorId=forked-path -Ddry-run=true release:prepare
mvn -DmavenExecutorId=invoker -Ddry-run=true release:prepare
Though if the configuration for the release plugin in your pom.xml or a
parent pom.xml is setting the value you will likely need to edit the
pom.xml to change the value.
On 14 May 2013 11:11, José Manuel Castroagudín Silva
chavescesu...@gmail.com wrote:
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] -
http://maven.apache.org/maven-release/maven-release-manager/apidocs/org/apache/maven/shared/release/exec/MavenExecutor.html
Thank you all,
2013/5/14 Graham Leggett minf...@sharp.fm
On 14 May 2013, at 10:02 AM, José Manuel Castroagudín Silva
chavescesu...@gmail.com 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
http://jira.codehaus.org/browse/MRELEASE-428 ).
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Saúde,
J. M. Castroagudín
--
Saúde,
J. M. Castroagudín
Re: release plugin, different executable name ('mvn3')
What about just a simple symlink (mvn -- mvn3) on your own account? you
don't need any system (root) permission, you create it yourself in your
account in one of your folders in your PATH
Alejandro Endo | Software Designer/Concepteur de logiciels
From: José Manuel Castroagudín Silva chavescesu...@gmail.com
To: Maven Users List users@maven.apache.org,
Date: 14/05/2013 04:38 AM
Subject:Re: release plugin, different executable name ('mvn3')
@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 chavescesu...@gmail.com
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 minf...@sharp.fm
On 14 May 2013, at 08:31, José Manuel Castroagudín Silva
chavescesu...@gmail.com 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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Saúde,
J. M. Castroagudín
--
Saúde,
J. M. Castroagudín
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use or deliver this message to anyone. In such event, you
should destroy the message and kindly notify the sender by reply
e-mail. It is understood that opinions or conclusions that do not
relate to the official business of the company are neither given
nor endorsed by the company.
Thank You.
