-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception when adding OSGi aspect after upgrade to v0.12. #144
Comments
That looks strange. Did you see the version number in the exception? |
Yes. The problem is that the OSGi version of the xstream-1.4.8-sources bundle is erroneous: Maybe some OSGi related sanity checks should be run when importing artifacts into a channel with the OSGi aspect enabled. See e.g. the following screenshot: I think the import test report should uncheck the xstream-1.4.8-sources bundle and tell the user that the version information in the OSGi manifest file is erroneous (like it did with the missing xmlpull javadoc and sources artifacts). By the way. When adding the OSGi aspect after importing the artifacts you will get the following stacktrace: import_after_aspects.txt |
Ok, this I clearly a case then for the OSGi validator. I already detects and reports illegal bundle symbolic names. So the artifact would be uploaded, but not processed as OSGi bundle. And a validation error would be attached to the artifact and channel. |
This looks perfectly fine to me. Thanks for coming up with a fix that quick :-) |
I have upgraded from package drone version 0.11 to 0.12.1.20160211-1555. When adding the OSGi aspect I get an exception. Adding other aspects works so far.
Attached files:
The text was updated successfully, but these errors were encountered: