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

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

I think I agree that it is not clear using the bundle version as the default 
package version makes sense. However, I'm not against having that as an option 
if someone wants it. However, we should probably do it like Peter suggests and 
somehow do it after the fact so bnd can attempt to figure things out first.

So, can we rollback the PackageVersionAnalyzer class and figure out a different 
way to handle this requirement? If so, then I can eliminate the patched Builder 
class and we close this issue.

> 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.

Reply via email to