You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "René Zanner (JIRA)" <ji...@apache.org> on 2008/11/20 17:34:44 UTC
[jira] Created: (FELIX-831) bndlib unnecessary modifies valid OSGi
Bundle-Version numbers (update to bndlib 0.0.293)
bndlib unnecessary modifies valid OSGi Bundle-Version numbers (update to bndlib 0.0.293)
----------------------------------------------------------------------------------------
Key: FELIX-831
URL: https://issues.apache.org/jira/browse/FELIX-831
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-1.4.3
Reporter: René Zanner
The current release of the plugin uses bndlib version 0.0.255.
In this version there is a bug converting valid OSGi Bundle-Version values to a different one.
A short summary: In my company we have a unusual versioning scheme - here is one example:
1.3.0.0-0-01-0
in development cycles extended by -SNAPSHOT: 1.3.0.0-0-01-0-SNAPSHOT. Both versions are - from the point of view of the OSGi spec - a valid Bundle-Version value (see the API here: http://www.osgi.org/javadoc/r4v41/org/osgi/framework/Version.html#Version(java.lang.String)).
In spite of this fact the maven-bundle-plugin (resp. bndlib) converts it to
1.3.0.0
or - when using -SNAPSHOT - 1.3.0.SNAPSHOT.
I already asked Peter Kriens to fix that and he quickly came up with a fix (version 0.0.293, to be downloaded from http://www.aqute.biz/repo/biz/aQute/bndlib/0.0.293/bndlib-0.0.293.jar).
I tried to replace the bndlib dependency with the new version. Unfortunately there seems to have been a significant change in the API of bndlib:
java.lang.NoClassDefFoundError: aQute/lib/reporter/Reporter
at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:360)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:273)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218)
Since it's not acceptable that a valid Bundle-Version is modified and I cannot use the most current version of bndlib, I ask you to update the maven-bundle-plugin to use a newer version of bndlib to fix the bug I mentioned above.
Thank you!
Regards,
René
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-831) bndlib unnecessary modifies valid OSGi
Bundle-Version numbers (update to bndlib 0.0.293)
Posted by "René Zanner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
René Zanner updated FELIX-831:
------------------------------
Fix Version/s: maven-bundle-plugin-1.6.0
Since I require this fixed rather urgently, I want this to bw the next planned version...
> bndlib unnecessary modifies valid OSGi Bundle-Version numbers (update to bndlib 0.0.293)
> ----------------------------------------------------------------------------------------
>
> Key: FELIX-831
> URL: https://issues.apache.org/jira/browse/FELIX-831
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.3
> Reporter: René Zanner
> Fix For: maven-bundle-plugin-1.6.0
>
>
> The current release of the plugin uses bndlib version 0.0.255.
> In this version there is a bug converting valid OSGi Bundle-Version values to a different one.
> A short summary: In my company we have a unusual versioning scheme - here is one example:
> 1.3.0.0-0-01-0
> in development cycles extended by -SNAPSHOT: 1.3.0.0-0-01-0-SNAPSHOT. Both versions are - from the point of view of the OSGi spec - a valid Bundle-Version value (see the API here: http://www.osgi.org/javadoc/r4v41/org/osgi/framework/Version.html#Version(java.lang.String)).
> In spite of this fact the maven-bundle-plugin (resp. bndlib) converts it to
> 1.3.0.0
> or - when using -SNAPSHOT - 1.3.0.SNAPSHOT.
> I already asked Peter Kriens to fix that and he quickly came up with a fix (version 0.0.293, to be downloaded from http://www.aqute.biz/repo/biz/aQute/bndlib/0.0.293/bndlib-0.0.293.jar).
> I tried to replace the bndlib dependency with the new version. Unfortunately there seems to have been a significant change in the API of bndlib:
> java.lang.NoClassDefFoundError: aQute/lib/reporter/Reporter
> at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:360)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:273)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218)
> Since it's not acceptable that a valid Bundle-Version is modified and I cannot use the most current version of bndlib, I ask you to update the maven-bundle-plugin to use a newer version of bndlib to fix the bug I mentioned above.
> Thank you!
> Regards,
> René
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (FELIX-831) bndlib unnecessary
modifies valid OSGi Bundle-Version numbers (update to bndlib 0.0.293)
Posted by "René Zanner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651500#action_12651500 ]
rzanner edited comment on FELIX-831 at 11/28/08 12:53 AM:
--------------------------------------------------------------
Since I require this fixed rather urgently, I want this to be in the next planned version...
was (Author: rzanner):
Since I require this fixed rather urgently, I want this to bw the next planned version...
> bndlib unnecessary modifies valid OSGi Bundle-Version numbers (update to bndlib 0.0.293)
> ----------------------------------------------------------------------------------------
>
> Key: FELIX-831
> URL: https://issues.apache.org/jira/browse/FELIX-831
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.3
> Reporter: René Zanner
> Fix For: maven-bundle-plugin-1.6.0
>
>
> The current release of the plugin uses bndlib version 0.0.255.
> In this version there is a bug converting valid OSGi Bundle-Version values to a different one.
> A short summary: In my company we have a unusual versioning scheme - here is one example:
> 1.3.0.0-0-01-0
> in development cycles extended by -SNAPSHOT: 1.3.0.0-0-01-0-SNAPSHOT. Both versions are - from the point of view of the OSGi spec - a valid Bundle-Version value (see the API here: http://www.osgi.org/javadoc/r4v41/org/osgi/framework/Version.html#Version(java.lang.String)).
> In spite of this fact the maven-bundle-plugin (resp. bndlib) converts it to
> 1.3.0.0
> or - when using -SNAPSHOT - 1.3.0.SNAPSHOT.
> I already asked Peter Kriens to fix that and he quickly came up with a fix (version 0.0.293, to be downloaded from http://www.aqute.biz/repo/biz/aQute/bndlib/0.0.293/bndlib-0.0.293.jar).
> I tried to replace the bndlib dependency with the new version. Unfortunately there seems to have been a significant change in the API of bndlib:
> java.lang.NoClassDefFoundError: aQute/lib/reporter/Reporter
> at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:360)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:273)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218)
> Since it's not acceptable that a valid Bundle-Version is modified and I cannot use the most current version of bndlib, I ask you to update the maven-bundle-plugin to use a newer version of bndlib to fix the bug I mentioned above.
> Thank you!
> Regards,
> René
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-831) bndlib unnecessary modifies valid
OSGi Bundle-Version numbers (update to bndlib 0.0.293)
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649403#action_12649403 ]
Stuart McCulloch commented on FELIX-831:
----------------------------------------
Yes, the latest development version of Bnd is very different and requires Java5 - so this will be a major version update to the bundleplugin (1.6.0)
There are a number of other potentially breaking changes targeting this version, and so I don't yet know exactly when it will be ready for release.
> bndlib unnecessary modifies valid OSGi Bundle-Version numbers (update to bndlib 0.0.293)
> ----------------------------------------------------------------------------------------
>
> Key: FELIX-831
> URL: https://issues.apache.org/jira/browse/FELIX-831
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.3
> Reporter: René Zanner
>
> The current release of the plugin uses bndlib version 0.0.255.
> In this version there is a bug converting valid OSGi Bundle-Version values to a different one.
> A short summary: In my company we have a unusual versioning scheme - here is one example:
> 1.3.0.0-0-01-0
> in development cycles extended by -SNAPSHOT: 1.3.0.0-0-01-0-SNAPSHOT. Both versions are - from the point of view of the OSGi spec - a valid Bundle-Version value (see the API here: http://www.osgi.org/javadoc/r4v41/org/osgi/framework/Version.html#Version(java.lang.String)).
> In spite of this fact the maven-bundle-plugin (resp. bndlib) converts it to
> 1.3.0.0
> or - when using -SNAPSHOT - 1.3.0.SNAPSHOT.
> I already asked Peter Kriens to fix that and he quickly came up with a fix (version 0.0.293, to be downloaded from http://www.aqute.biz/repo/biz/aQute/bndlib/0.0.293/bndlib-0.0.293.jar).
> I tried to replace the bndlib dependency with the new version. Unfortunately there seems to have been a significant change in the API of bndlib:
> java.lang.NoClassDefFoundError: aQute/lib/reporter/Reporter
> at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:360)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:273)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218)
> Since it's not acceptable that a valid Bundle-Version is modified and I cannot use the most current version of bndlib, I ask you to update the maven-bundle-plugin to use a newer version of bndlib to fix the bug I mentioned above.
> Thank you!
> Regards,
> René
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-831) bndlib unnecessary modifies valid OSGi
Bundle-Version numbers (update to bndlib 0.0.293)
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch resolved FELIX-831.
------------------------------------
Resolution: Fixed
Fixed in trunk with the update to Bnd 0.0.295 - however, note that I'm still testing this against various projects to check for any build breaks.
I also hope to have a stable snapshot that people can start testing themselves by the end of this week.
> bndlib unnecessary modifies valid OSGi Bundle-Version numbers (update to bndlib 0.0.293)
> ----------------------------------------------------------------------------------------
>
> Key: FELIX-831
> URL: https://issues.apache.org/jira/browse/FELIX-831
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.3
> Reporter: René Zanner
> Fix For: maven-bundle-plugin-1.6.0
>
>
> The current release of the plugin uses bndlib version 0.0.255.
> In this version there is a bug converting valid OSGi Bundle-Version values to a different one.
> A short summary: In my company we have a unusual versioning scheme - here is one example:
> 1.3.0.0-0-01-0
> in development cycles extended by -SNAPSHOT: 1.3.0.0-0-01-0-SNAPSHOT. Both versions are - from the point of view of the OSGi spec - a valid Bundle-Version value (see the API here: http://www.osgi.org/javadoc/r4v41/org/osgi/framework/Version.html#Version(java.lang.String)).
> In spite of this fact the maven-bundle-plugin (resp. bndlib) converts it to
> 1.3.0.0
> or - when using -SNAPSHOT - 1.3.0.SNAPSHOT.
> I already asked Peter Kriens to fix that and he quickly came up with a fix (version 0.0.293, to be downloaded from http://www.aqute.biz/repo/biz/aQute/bndlib/0.0.293/bndlib-0.0.293.jar).
> I tried to replace the bndlib dependency with the new version. Unfortunately there seems to have been a significant change in the API of bndlib:
> java.lang.NoClassDefFoundError: aQute/lib/reporter/Reporter
> at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:360)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:273)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218)
> Since it's not acceptable that a valid Bundle-Version is modified and I cannot use the most current version of bndlib, I ask you to update the maven-bundle-plugin to use a newer version of bndlib to fix the bug I mentioned above.
> Thank you!
> Regards,
> René
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-831) bndlib unnecessary modifies valid OSGi
Bundle-Version numbers (update to bndlib 0.0.293)
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch reassigned FELIX-831:
--------------------------------------
Assignee: Stuart McCulloch
> bndlib unnecessary modifies valid OSGi Bundle-Version numbers (update to bndlib 0.0.293)
> ----------------------------------------------------------------------------------------
>
> Key: FELIX-831
> URL: https://issues.apache.org/jira/browse/FELIX-831
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.3
> Reporter: René Zanner
> Assignee: Stuart McCulloch
> Fix For: maven-bundle-plugin-1.6.0
>
>
> The current release of the plugin uses bndlib version 0.0.255.
> In this version there is a bug converting valid OSGi Bundle-Version values to a different one.
> A short summary: In my company we have a unusual versioning scheme - here is one example:
> 1.3.0.0-0-01-0
> in development cycles extended by -SNAPSHOT: 1.3.0.0-0-01-0-SNAPSHOT. Both versions are - from the point of view of the OSGi spec - a valid Bundle-Version value (see the API here: http://www.osgi.org/javadoc/r4v41/org/osgi/framework/Version.html#Version(java.lang.String)).
> In spite of this fact the maven-bundle-plugin (resp. bndlib) converts it to
> 1.3.0.0
> or - when using -SNAPSHOT - 1.3.0.SNAPSHOT.
> I already asked Peter Kriens to fix that and he quickly came up with a fix (version 0.0.293, to be downloaded from http://www.aqute.biz/repo/biz/aQute/bndlib/0.0.293/bndlib-0.0.293.jar).
> I tried to replace the bndlib dependency with the new version. Unfortunately there seems to have been a significant change in the API of bndlib:
> java.lang.NoClassDefFoundError: aQute/lib/reporter/Reporter
> at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:360)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:273)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227)
> at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218)
> Since it's not acceptable that a valid Bundle-Version is modified and I cannot use the most current version of bndlib, I ask you to update the maven-bundle-plugin to use a newer version of bndlib to fix the bug I mentioned above.
> Thank you!
> Regards,
> René
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.