On Wednesday 20 October 2004 17:31, Eric Pugh wrote:
Hi,
Quite a few of the Jakarta Turbine Fulcrum components use the javamail-1.3.1.jar version of JavaMail. Currently Gump has javamail-1.3 installed. Can we have this dependency upgraded? This will remove the last obstacle to our components compiling under Gump.
This is not about 1.3 vs 1.3.1, never was...
Please proceed and change to whatever version you like.
Now, the problem is about the 'exposure' of the Jar's from their names on the Brutus filesystem, vs the name expected in your projects.
Stefano gave me heads up earlier that he is tackling this in a generic fashion, since it won't scale if we go in and ask for changes in each project.
That means that we will be able to declare in the Gump descriptor that abc.jar is used for an def-x.y.z.jar by Maven (and others), so that in the overrides file,
maven.jar.override = on maven.jar.abc = /usr/local/...../javamail/mail.jar
is generated. This will solve all projects with a similar situation and allowing all the existing ant-wrappers for Maven projects to go away.
So, just hang in tight, and the problem will be solved at Gump's end.
I just discussed this with Adam and he suggested that rather than introducing further complexity in the metadata, we change the exposed jar ID so that they match maven's.
What is the maven ID for the mail.jar package?
Is there a search engine for maven artifacts?
-- Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
