> -----Original Message-----
> From: Daniel Fagerstrom [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 26, 2005 9:17 AM
> To: [email protected]
> Subject: Re: jar naming convention
>
> Typical naming of Apache jars assume that the context
> (Apache) is known.
> This assumption breaks down with jar repositories and bundle
> repositorires, where the Eclipse naming convention makes much
> more sense, as the names are granted to be unique and the
> source of the jar
> (bundle) is obvious. IMO we should go for the Eclipse way in Felix.
>
(Brent, keep me straight here...)
Maven2 introduces greater degree of contextualization with respect to
jar repository organization conventions. For instance, groupId's can
now be named *org.apache.felix.framework* and the artifactId can remain
*felix* and the version can be specified as *2.0.1*.
This would result in the following jar being stored in the ibiblio
maven2 repo as...
/maven2
/org
/apache
/felix
/framework
/felix
/2.0.0
felix-2.0.0.jar
felix-2.0.0.pom
/2.0.1
felix-2.0.1.jar
felix-2.0.0.pom
...
You can see this explicitly at
http://www.ibiblio.org/maven2/org/eclipse/jdt/core/.
The resultant maven dependency reference in a maven POM would look like:
<dependency>
<groupId>org.apache.framework/groupId>
<artifactId>felix</artifactId>
<version>2.0.1</version>
</dependency>
Does this provide you with the context you desire, or do you really need
for the context to be completely self-evident in the artifact's full
file name?
-tbennett
