Hi all,

a colleague of mine ran into a problem and created a forum entry in the
JBoss AS 7 section, but I thought it might be a good fit here.

The entry is https://community.jboss.org/thread/205456

I searched a bit around and found
https://community.jboss.org/thread/165717 where Thomas showed an example
MANIFEST.MF without any versions (I assume 7.0.0 used the latest
available one?)

Now the question is: Was it an intended change that the version has now
to be specified and the follow-up if the answer is yes: What is the
recommended behaviour of dealing with "hotfixes".

A simple example: We have a bunch of EJBs all referencing a small
utility bundle in version 1.0.0. Now we discover a bug in the utility
bundle and release a new version (1.0.1 according to the OSGi semantic
versioning spec) but all of our EJBs refer to the 1.0.0, so in that case
we would have to change / release all of our EJBs as well, to refer to
the new bundle?

Leaving the version out of the dependencies seems not to work in JBoss 7.1.2

Greetings
-Sascha-
_______________________________________________
jboss-osgi-dev mailing list
jboss-osgi-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-osgi-dev