On 28/02/2010, Jan Matèrne wrote:
> I had a quick look at the buildfile [1].
> The calling target seems to be
>
>
>
>
>
>
> Maybe you could change that to allow specifying the absolute path:
>
>
>
> failonerror="true">
>
>
>
>
> and then add a mvn.dir=... optio
I had a quick look at the buildfile [1].
The calling target seems to be
Maybe you could change that to allow specifying the absolute path:
and then add a mvn.dir=... option in Hudson.
Jan
[1]
http://svn.apache.org/repos/asf/jakarta/bsf/branches/bsf3.x/bsf-engines
On 28/02/2010, Jukka Zitting wrote:
> Hi,
>
>
> On Fri, Feb 26, 2010 at 7:44 PM, sebb 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
Hi,
On Fri, Feb 26, 2010 at 7:44 PM, sebb 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
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///
