> I don't really know what you are talking about here, but I'll give some
> background that might help.
That makes two of us then, so thanks for trying to bring us both to a better
understanding. :-)
> 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).
>From our previous exchanges on this (and my reading of the docs) I
understand that I have to set:
------------------------------------------------------------------------
# M A V E N J A R O V E R R I D E
# ------------------------------------------------------------------------
maven.jar.override = on
# ------------------------------------------------------------------------
# Jars set explicity by path.
# ------------------------------------------------------------------------
maven.jar.None=/var/gump/jakarta-gump-test/maven-project1/target/gump-test-m
aven1-0.1.jar
i.e. maven.jar.{id} in the build.properties file.
http://gump.dotnot.org/jakarta-gump-test/work/display_file_cat_build.properties.html
That means (AFAICT) we need the Gump jar 'id' to match the Maven project
artifact 'id' -- since Maven requires that I set each override explicitly --
and since Gump has only it's metadata to draw from (especially w/ non-Maven
projects.)
That is the issue, that marriage at the metadata level.
> There is a bug in RC1 where it reports succesful even if dependencies
fail -
> fixed in RC2 which is coming right up.
Thanks. Will install when ready.
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
