Carlos Sanchez wrote: > I'm uploading right now a good number of jars to > http://repo1.maven.org/eclipse-staging/ > If it looks good I will sync to central > > Note that the location for the one you want should be > http://repo1.maven.org/eclipse-staging/org/eclipse/core/resources/3.2.1/
I wonder if this groupId:artifactId mapping is a bad idea?
Most jars in the repository have an artifactId which is, whilst not
necessarily globally unique, good enough to give you a pretty good idea
what they are. This is a good thing, since there are several use cases
where a collection of jars is bundled into a single directory, and those
jars are named {artifactId}-{version}.jar (e.g, war file WEB-INF/lib/,
common usage of assembly plugin).
The suggested mapping of just taking the last component of the name as
the artifactId will lead to many artifacts with non-descriptive and
clashing names like "common", "core", "ui", etc. At best case, this
will merely be horrendously confusing for humans attempting to
understand and debug these generated collections of jars. At worst case,
some of the artifacts will not only have the same artifactId, but same
version too, and will overwrite each other.
So, I think the current mapping fits poorly with existing Maven
use-cases and plugin design, and needs further consideration.
Max.
signature.asc
Description: OpenPGP digital signature
