Not everyone is using OSGi ...so I doubt this is really an option to
prevent a package shift.
My 2 cents
--
Torsten
On 21.01.2008, at 09:13, Tom Schindl wrote:
Hi,
Couldn't this OSGi-adoption made by some commons packages make the
package shift for java5 unneeded?
With OSGi one can run different versions in the same JVM so its not
needed any more.
Tom
Niall Pemberton schrieb:
On Dec 28, 2007 2:39 PM, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
Two things:
- if the bundle plugin could be released, it'd be great, if not
projects won't be able to make a release
- my approach to add an osgified manifest to the current project is
different in order not to change the packaging to bundle. bundle
packaging only needs to be used to osgify 3rd party libraries. The
manifest goal of the bundle plugin will generate the OSGi
manifest for
any maven project.
I missed this originally - is there any reason to not use
packaging of
"bundle" and let the bundle plugin create the jar?
Seems like that would be an easy way to turn it on/off for components
(the recommendation for logging was to not do it).
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
