I meant the common maven way, which is <artifactName>-<artifactVersion>.jar.
I don't know if there is a common OSGi way defined. When I look at the files in osgi repo hosted by the osgi alliance, the files are using format such as org.eclipse.osgi-3.5.0.jar. Lin On Wed, Nov 25, 2009 at 3:16 PM, Mark Nuttall <[email protected]> wrote: > The first thing I found was "Respect OSGi naming conventions for db4o > bundle<http://tracker.db4o.com/browse/COR-1623>" > which includes a bundle name, com.db4o.osgi_7.4.71.12224.jar > > Is there a defined "OSGi naming convention" ? If there is, is eclipse seen > as conforming to it? Sample from a local install: > org.mortbay.jetty_5.1.14.v200806031611.jar > > I don't have a local maven install handy but Lin when you said "the common > way to do version" did you mean "the maven way" or "the OSGi way" or what? > The current name is of the form > aries-blueprint-1.0.0-incubating-SNAPSHOT.jar > > Regards, > Mark > > > 2009/11/25 Lin Sun <[email protected]> > >> See below for comments >> >> Lin >> >> On Wed, Nov 25, 2009 at 2:01 PM, Alasdair Nottingham >> <[email protected]> wrote: >> > DOH, I thought I tried that, but it does indeed appear to fix the >> problem. >> > >> > Do you know how to get the separator between the artifact id and the >> > version to be an '_' rather than a '-'? >> >> I dont. Honestly I have never seen anything produced from Maven that >> uses a '_' instead of a '-'. >> >> I am curious why you want to do that. If you look at the jars >> published in maven repo - http://repo1.maven.org/maven2/, I doubt you >> could find any that has a '_'. >> >> > Also I think the separator >> > between the version "1.0.0" and the build identifier should be a '.', >> > is that possible? >> >> I think that is possible by changing the following in blueprint/pom.xml >> >> <version>1.0.0-incubating-SNAPSHOT</version> >> >> but the common way to do version is to use what we have right now. >> >> > >> > Thanks >> > Alasdair >> > >> > 2009/11/25 Lin Sun <[email protected]>: >> >> Hi, >> >> >> >> I think this can be changed by modifying the pom file. for example, >> >> for blueprint-bundle: >> >> >> >> - <artifactId>aries-blueprint</artifactId> >> >> + <artifactId>org.apache.aries.blueprint</artifactId> >> >> >> >> I'd be happy to make the change if there is no objection. >> >> >> >> Lin >> >> >> >> >> >> On Wed, Nov 25, 2009 at 1:12 PM, Alasdair Nottingham >> >> <[email protected]> wrote: >> >>> Hi, >> >>> >> >>> The jar files generated by our build do not have the format I usually >> >>> expect for OSGi bundle jar files. I expect to see something of the >> >>> form: >> >>> >> >>> org.apache.aries.blueprint_1.0.0.incubating-SNAPSHOT.jar >> >>> >> >>> but instead we get: >> >>> >> >>> aries-blueprint-1.0.0-incubating-SNAPSHOT.jar >> >>> >> >>> I've had a look at the pom files, but I do not know how the jar file >> >>> name is generated, so I do not know how to change it to follow the >> >>> bundle naming convention. >> >>> >> >>> Does anyone know what needs to be done? >> >>> Thanks >> >>> Alasdair >> >>> >> >>> -- >> >>> Alasdair Nottingham >> >>> [email protected] >> >>> >> >> >> > >> > >> > >> > -- >> > Alasdair Nottingham >> > [email protected] >> > >> >
