[jira] Commented: (FELIX-2176) Upgrade maven-bundle-plugin to up to date bnd

["Richard S. Hall (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924040#action_12924040 ] 

Richard S. Hall commented on FELIX-2176:
----------------------------------------

I'm not against just keeping a copy of the BND code in our repo if it means we can do a better job of keeping BND up-to-date. It seems idiotic to be blocked by the lack of an artifact in a Maven repo.

I had worked with Peter a little while back on heuristics to try to improve how BND decides to import exported packages, since the original behavior was too simplistic and is resulting in the creation of lots of improperly defined bundle metadata. I think updating our plugin to a more recent version of BND is of paramount importance.

Does anyone have any objection to just directly including the BND source in our project?

> Upgrade maven-bundle-plugin to up to date bnd
> ---------------------------------------------
>
>                 Key: FELIX-2176
>                 URL: https://issues.apache.org/jira/browse/FELIX-2176
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.0.1
>            Reporter: David Jencks
>             Fix For: maven-bundle-plugin-2.1.0
>
>         Attachments: FELIX-2176.diff
>
>
> Peter doesn't seem to release bnd to public repos, but does have an accessible private repo.  The bundle plugin can copy bnd into itself so users don't have to have peter's secret stash configured in their nexus repo manager.
> Patch does this and upgrades to latest bnd.  I can't see any reason to keep the copied Builder source -- plugin passes tests and appears to work without it -- so I removed it.  You'll need to run
> svn rm    src/main/java/aQute/lib/osgi/Builder.java
> Also the code in   src/main/java/org/apache/felix/bundleplugin/PackageVersionAnalyzer.java _really_ doesn't compile any more and I suspect the functionality has moved into bnd.  However I can't actually tell what its trying to do; I commented it out.  If this functionality is actually in bnd then removing the class would be a good idea.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.