maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alejandro.E...@miranda.com
Subject Re: release plugin, different executable name ('mvn3')
Date Tue, 14 May 2013 17:01:32 GMT

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 <chavescesures@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 <chavescesures@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 <minfrin@sharp.fm>
>
>> On 14 May 2013, at 08:31, José Manuel Castroagudín Silva <
>> chavescesures@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@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.


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