Hi
In theory, there is no problem on releasing, because in that case,
${project.version} does not have qualifier. I did not found a way to
workaround this effect.
regards,
Leonardo Uribe
2010/7/5 Jakob Korherr <[email protected]>
> Hi,
>
> Just FYI: the require-bundle was introduced in revision 933820 in
> MYFACES-2290.
>
> Regards,
> Jakob
>
> 2010/7/5 Mark Struberg <[email protected]>
>
> Hi!
>>
>> I fooled around digging into OSGi container internals, maven plugins, etc
>> for 2 hours to find a small issue in our pom finally :)
>>
>>
>> in myfaces-api we define the following
>>
>>
>> <Require-Bundle>org.apache.myfaces.core.impl;bundle-version="${project.version}"</Require-Bundle>
>>
>> Now, while trying to install this bundle to geronimo-3 for building an
>> updated geronimo-myfaces plugin, I always crashed with a
>> NumberFormatException.
>>
>> This has the following reason:
>>
>> An OSGi version consiste of [a].[n].[b].[q] always separeted by a dot.
>> a..mAjor number
>> n..miNor number
>> b..Build number
>> q..Qualifier
>>
>> a,n,b _must_ be numeric
>> q might be alphanumeric
>>
>> In our myfaces-api/pom.xml we have the following maven-bundle-plugin
>> configuration:
>>
>> Because of using ${project.version} in the <Require-Bundle>, we get the
>> following version written to our manifest: 2.0.1-SNAPSHOT, which is an
>> invalid OSGi version. A valid one would be 2.0.1.SNAPSHOT (dot instead of -)
>>
>> I'm not sure how we should cope with this in the future though...
>>
>> LieGrue,
>> strub
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
