Page History

...

Repositories can be any combination of these.

POM referencing

The POM will always reference the primary artifact.

The conflict ID of a dependnecy is:
groupId:artifactId:type
and the full versioned ID is
groupId:artifactId:type:version

Subtypes are created by particular mojos: eg ejb packaging will create both an ejb and an ejb-client. apidocs:package will create a JAR of the javadocs.

Dependencies will generally only reference the type corresponding to the packaging. However, in some cases, dependency on a subtype will also be required, eg:
<type>ejb-client</type>.
This subtype will be mapped to the same artifact handler that deals with the ejb packaging so that main POM can be found.

Alternatively, we could drop the extension and always use:
.../plexus-container-0.15-200407151214.pom
instead of
.../plexus-container-0.15-200407151214.jar.pom

This change is not currently planned.

This would require that one artifact ID only ever be associated to one packaging, which is a best practice. The only opposing use case seems to be something such as a TLD - however this is really a subtype of a taglib JAR.