gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject RE: Maven/Gump & Artefact/Jar Identifiers
Date Wed, 05 May 2004 23:00:49 GMT

I think artifact ID = jar ID, as the resultant filename in a repository is
always artifactId-version.jar

Whether the artifact ID or jar ID gets changed is probably on a project by
project basis.

I'm not entirely convinced myself though, and it would be worth getting an
opinion on maven-dev.


> -----Original Message-----
> From: Adam R. B. Jack [] 
> Sent: Thursday, 6 May 2004 3:29 AM
> To: Gump code and data
> Subject: Maven/Gump & Artefact/Jar Identifiers
> I tinkered with using Maven to build commons-id. Some 
> success, but the problems come down to artefact identifiers. 
> I.e. commons logging is passed as a dependency (in the 
> file), but the 'Maven jar override' fails to 
> kick in 'cos the jar id (all) is different from the artefact 
> id (commons-logging).

[please forgive the wrap bug] The salient lines are below:

# Note 'all' not 'commons-logging':

This page shows the problem quite well:

So, question. Do we try to rename all jar identifiers to match Maven
artefact identifiers (semi-appealing, if there isn't some gotcha) or do we
add a new attribute 'artefactId' to fullfill this role? Any other

Please let me know if I've not explain the problem well enough.


Experience the Unwired Enterprise:
Try Sybase:

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message