You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by Carsten Ziegeler <cz...@apache.org> on 2008/12/17 14:20:54 UTC
Portlet API 2.0 jar is missing bundle version in maven repo
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 :(
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Portlet API 2.0 jar is missing bundle version in maven repo
Posted by Scott O'Bryan <da...@gmail.com>.
Did we have a resolution on this? I personally agree with the way
geronimo does things. The produced jars are completely correct, they
are just named different things.
Scott
David Jencks wrote:
> This is why the geronimo spec jars are named
> geronimo-<spec-name>_<spec-version>_spec with a maven version
> indicating the revision of the jar, not the spec.
>
> We quickly found that despite our best efforts we often had to fix
> problems in our tck-passing spec jars and after a lot of discussion
> settled on this scheme.
>
> thanks
> david jencks
>
> On Dec 17, 2008, at 10:20 AM, Carsten Ziegeler wrote:
>
>> Ate Douma wrote:
>>> 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.
>> Yes, that's why I'm asking here :)
>>
>>> 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.
>> Hmm, maybe they make an exception here, but nevertheless the wrong jar
>> is out there, downloaded from the central repo.
>>
>> So, what if we would name the version 2.0a or something like that?
>> Or 2.0-final? So I guess we can come up with a name that makes sense
>> and gets accepted from the spec group?
>> In addition we can ask for removal of the faulty jar from the repo.
>>
>> Carsten
>>
>> --
>> Carsten Ziegeler
>> cziegeler@apache.org
>
RE: Portlet API 2.0 jar is missing bundle version in maven repo
Posted by "Noel J. Bergman" <no...@devtech.com>.
> This is why the geronimo spec jars are named geronimo-<spec-
> name>_<spec-version>_spec with a maven version indicating the
> revision of the jar, not the spec.
Likewise, Ubuntu packages are generally of the form package-<package
version>-<ubuntu revision>, e.g.,
transmission-common 1.42-0ubuntu1
See
http://www.ducea.com/2006/06/17/ubuntu-package-version-naming-explanation/
for details.
In this case, the artifact hasn't changed, just the Maven meta-data.
--- Noel
Re: Portlet API 2.0 jar is missing bundle version in maven repo
Posted by David Jencks <da...@yahoo.com>.
This is why the geronimo spec jars are named geronimo-<spec-
name>_<spec-version>_spec with a maven version indicating the
revision of the jar, not the spec.
We quickly found that despite our best efforts we often had to fix
problems in our tck-passing spec jars and after a lot of discussion
settled on this scheme.
thanks
david jencks
On Dec 17, 2008, at 10:20 AM, Carsten Ziegeler wrote:
> Ate Douma wrote:
>> 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.
> Yes, that's why I'm asking here :)
>
>> 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.
> Hmm, maybe they make an exception here, but nevertheless the wrong jar
> is out there, downloaded from the central repo.
>
> So, what if we would name the version 2.0a or something like that?
> Or 2.0-final? So I guess we can come up with a name that makes sense
> and gets accepted from the spec group?
> In addition we can ask for removal of the faulty jar from the repo.
>
> Carsten
>
> --
> Carsten Ziegeler
> cziegeler@apache.org
Re: Portlet API 2.0 jar is missing bundle version in maven repo
Posted by Carsten Ziegeler <cz...@apache.org>.
Ate Douma wrote:
> 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.
Yes, that's why I'm asking here :)
> 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.
Hmm, maybe they make an exception here, but nevertheless the wrong jar
is out there, downloaded from the central repo.
So, what if we would name the version 2.0a or something like that?
Or 2.0-final? So I guess we can come up with a name that makes sense
and gets accepted from the spec group?
In addition we can ask for removal of the faulty jar from the repo.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Portlet API 2.0 jar is missing bundle version in maven repo
Posted by Ate Douma <at...@douma.nu>.
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