Comments inline.
At 01:32 AM 1/31/2007, John E. Conlon wrote:
>Peter Kriens' Bnd tool for OSGi bundle creation is a very handy tool for
>creating and verifying bundles.
>See: http://www.aqute.biz/Code/Bnd
>
>I used it to verify our maven created jars and it reported a couple of
>errors with our OSGi metadata. Here is an example of the output from
>the tool:
[snip]
>4 : Invalid value for Bundle-Version, 1.3-SNAPSHOT does not match
>[0-9]+(\.[0-9]+(\.[0-9]+(\.[0-9A-Za-z_-]+)?)?)?
Reading the above message, I would say that "1.3-SNAPSHOT" is not a legal
version number but "1.3.0-SNAPSHOT" is. So we can perhaps retain
<Bundle-Version>${project.version}</Bundle-Version>
instead of
<Bundle-Version>1.3.0.SNAPSHOT</Bundle-Version>
in pom.xml, subject to the condition that ${project.version} equals
"1.3.0-SNAPSHOT" or 1.3.0 or 1.3 but not 1.3-SNAPSHOT.
>Would it cause anyone any pain if we removed the Bundle-Classpath from
>our manifests?
The current manifest entries mimic the entires found in Spring-OSGi (see
[1]). I don't mind if they are removed although I wonder why they are
present in spring-osgi.
Cheers,
[1]
http://svn.sourceforge.net/viewvc/springframework/spring-osgi/trunk/spring-modules/spring-required-libraries/slf4j-api/META-INF/MANIFEST.MF?view=log
>kind regards,
>John
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
