Guillaume Nodet wrote:
I think it would make sense to follow what geronimo did for the same problem.
As the jars discussed are spec jars, it would make sense to just
change the artifactId to include the version of the spec inside it:
So it would give:
groupId: org.apache.felix
artifactId: org.osgi.core-4.0.0
version: 1.0.4
The reasoning behing that is that the spec for 4.0 and 4.1 will be
different and you may not want maven to automatically select the 4.1
which would have a greater version than any 4.0.
AFAIK, maven can handle specific version for artifact and even version
range, so (due to my limit) I can't image a scenario where org.osgi.core
break while org.osgi.core-4.0.0 works. Can you provide me a use case
covering showing the benefit of org.osgi.core-4.0.0?
My 2 cents.
On Wed, Mar 12, 2008 at 5:56 PM, Stefano Lenzi <[EMAIL PROTECTED]> wrote:
Hi All,
As discussed on the thread:
http://www.mail-archive.com/dev@felix.apache.org/msg03733.html
A new version schema for org.osgi.* module has been proposed. The new
version schema is the one already in use by the Apache Felix Common
subproject.
For example if the new version schema will be approved the already
released artifact org.osgi.core:1.0.0, org.osgi.compedium:1.0.0, and
org.osgi.foundation:1.0.0 will be re-released as
org.osgi.core:4.0.0-001, org.osgi.compedium:4.0.0-001, and
org.osgi.foundation:4.0.0-001 respectively.
So please cast your votes
[ ] +1 Use new version schema for org.osgi.* module
[ ] 0 Don't care.
[ ] -1 Keep the old name schema
Vote will run for *72hrs* - only PMC votes will be binding, but anyone
can vote
Ciao,
Stefano "Kismet" Lenzi
