You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Antoine Lévy-Lambert <an...@antbuild.com> on 2004/03/15 21:28:00 UTC
Re: build of jakarta-pluto - gump or gumpy problem ?[was : Persian
enigma]
Antoine Lévy-Lambert wrote:
> The project descriptor for jakarta-pluto says this :
>
> <jar id="container" name="container/target/pluto-1.0.jar"/>
> <jar id="api" name="api/target/portlet-api-1.0.jar"/>
> <jar id="portal" name="portal/target/pluto-portal-impl-1.0.jar"/>
>
> and the jars exist at these locations, ie for instance :
> /data3/gump/jakarta-pluto/container/target/pluto-1.0.jar
> but gumpy looks for :
> /data3/gump/jakarta-pluto/temp/container/target/pluto-1.0.jar
> which does not exist.
>
> the jakarta-pluto.xml file also contains these lines :
> <mkdir dir="temp/api/classes/"/>
> <mkdir dir="temp/container/classes/"/>
> <home nested="temp"/>
>
>
>
I think I misqualified the problem.
I have just changed the project descriptor for jakarta-pluto, removing
these home related settings.
I wonder whether, to the contrary, traditional gump does not check the
presence of the jars listed in the descriptor.
And should check ?
Cheers,
Antoine
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org