Carsten Ziegeler wrote:
Hi,
I just noticed that the portlet api jar available from the central maven
repo is missing the bundle version manifest entry (Bundle-Version: 2.0).
Without the version information the jar is unusable in an OSGi environment.
I'm not sure what the best way to fix this is :(
Well, this definitely might be problematic.
I just reviewed the manifest configuration in the portlet2-api module (actually committed by yourself, r649499) and indeed it doesn't match
up the manifest configuration as provided through the final release portlet20.jar.
Fixing the manifest configuration in the portlet2-api/pom.xml is easy enough to do, but getting an updated jar distributed to the central
maven repo might be a problem.
AFAIK, the policy on the maven repo is *not* to override any earlier "released"
artifact.
The default answer to that is "just put out a new minor release".
But that's something we cannot do as this is not "our" artifact but the formal
JSR-286 2.0 release :(
Maybe you know if there is some way around the "not override" policy in the
central maven repo (like asking very nicely)?
The rsync to the central repo is managed by the repository team, so maybe best
thing is ask there.
Regards,
Ate
Carsten
