Hi Adam,

I don't really know what you are talking about here, but I'll give some
background that might help.

In the project.xml, currently <id> is the "artifactId" (it will at some time
be renamed as such). JAR files are usually constructed as
artifactId-version.jar, where version is given by currentVersion (which will
also be renamed for consistency).

There is a bug in RC1 where it reports succesful even if dependencies fail -
fixed in RC2 which is coming right up. 

Hope this helps,
Brett

> -----Original Message-----
> From: Adam R. B. Jack [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, 11 February 2004 3:07 AM
> To: Gump code and data
> Subject: Gump & Maven -- plodding along...
> 
> 
> Ok, so some progress, some odd stuff:
> 
> http://gump.dotnot.org/jakarta-gump-test/index.html
> 
>     
> --------------------------------------------------------------------
> 
> So I'm writing the build.properties file, but see the 'None' 
> below, that ought be the "id" of the jar.
> 
> 1) I'm not quite sure what to do when a Gump <jar doesn't set 
> an id, I suspect I have to manufacture one. If only one jar 
> in a project, perhaps I use the project name. If more, then 
> what? Perhaps manufacture one from the basename of the jar or 
> something?
> 
> 2) I'm a little concerned that we need to get the exact jar 
> id for Maven, and I hope that somehow that can tie with 
> Gump's jar id. Any views here?
> 
http://gump.dotnot.org/jakarta-gump-test/work/display_file_cat_build.propert
ies.html


maven.jar.None=/var/gump/jakarta-gump-test/maven-project1/target/gump-test-m
aven1-0.1.jar

    --------------------------------------------------------------------

Why does this return an exit code of success, when it states it failed?

http://gump.dotnot.org/jakarta-gump-test/work/build_jakarta-gump-test_gump-t
est-maven2.html

regards,

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to