On 28 Mar 07, at 9:15 AM 28 Mar 07, Damien Lecan wrote:
> How this will be done ?
At first by putting an innocuous plugin in the lifecycle, or in 2.1
with extensions in Plexus it will be an extension to the JAR plugin
that populates manifest information.
It would be great if that could be available in 2.0.x version of
Maven. We are too far from 2.1 version.
Changing the lifecycle is not technically hard but it's still a
change at a very fundamental level. I don't see this going into 2.0.x.
> Will it be active by default ?
If we decide that it's non-invasive and doesn't significantly
increase the time of anyone's builds then I see so harm.
Ok I understand, but you didn't answer my (not clear) question : if
OSGi packaging is fast enough, will OSGi manifest entries be
transparently added to every maven-build jars ?
Yes, they would be transparently added provided it is entirely non-
invasive and the performance impact is slight.
Or will it be an OSGi developer option, that will never be known and
used by other common people ?
Commons users will never see it. We're not pushing OSGi
configurations in people's faces.
Jason.
Thanks
Damien
---------------------------------------------------------------------
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]
