You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by sebb <se...@gmail.com> on 2010/02/26 19:44:57 UTC

[Hudson] Command "mvn" not found

Jakarta BSF 3 uses M2 to build.

The M2 build includes an Ant task, which in turn invokes "mvn" in
order to do an install.

This fails on Hudson.

Is there a way to call Maven from Ant?

Or perhaps a Maven guru can suggest how to rewrite the BSF pom
eliminate the nested Maven call ?

S///

Re: [Hudson] Command "mvn" not found

Posted by sebb <se...@gmail.com>.
On 28/02/2010, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
>
>  On Fri, Feb 26, 2010 at 7:44 PM, sebb <se...@gmail.com> wrote:
>  > The M2 build includes an Ant task, which in turn invokes "mvn" in
>  > order to do an install.
>  >
>  > This fails on Hudson.
>
>
> That's because "mvn" is not on the default PATH. The latest Maven 2
>  executable is at ~hudson/tools/maven/latest2/bin/mvn.
>

OK, so how does one add this to the PATH?

>
>  > Or perhaps a Maven guru can suggest how to rewrite the BSF pom
>  > eliminate the nested Maven call ?
>
>
> As commented in the build.xml file, using the Maven Assembly plugin
>  for this seems like the obvious solution.

The build file does quite a lot of complicated work; it's not at all
obvious to me how the assembly plugin can be persuaded to do it.

>  BR,
>
>
>  Jukka Zitting
>

Re: [Hudson] Command "mvn" not found

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Fri, Feb 26, 2010 at 7:44 PM, sebb <se...@gmail.com> wrote:
> The M2 build includes an Ant task, which in turn invokes "mvn" in
> order to do an install.
>
> This fails on Hudson.

That's because "mvn" is not on the default PATH. The latest Maven 2
executable is at ~hudson/tools/maven/latest2/bin/mvn.

> Or perhaps a Maven guru can suggest how to rewrite the BSF pom
> eliminate the nested Maven call ?

As commented in the build.xml file, using the Maven Assembly plugin
for this seems like the obvious solution.

BR,

Jukka Zitting