On 6 Mar 2013, at 15:15, Andrew Kenney wrote:

> Hi Stuart,
> 
> There's an open JIRA issue for the maven bundle plugin that would be very 
> useful to have in the new release.
> https://issues.apache.org/jira/browse/FELIX-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel
> 
> I did some investigation into using OBR last October, but concluded that it 
> was not very useful if the maven bundle plugin couldn't place my project's 
> dependencies into my OBR repo, along with the project's artifact.
> I've tried to use the proposed setting with the latest plugin, but it didn't 
> work.
>       <addDependenciesToRepository>true</addDependenciesToRepository>
> 
> Do you think this feature would be possible to add?
> 
> In my opinion, OBR has some deficiencies... but if the maven bundle plugin 
> had this capability, it overcomes a majority of OBRs problems.  OBR is pretty 
> useless if repository maintenance isn't automated.

I'll take a look as part of the ongoing bug triage - btw, if anyone else is 
interested in this feature (or any others) you can vote for it on JIRA.

> Thanks for your consideration,
> Andrew
> 
> -----Original Message-----
> From: Stuart McCulloch [mailto:[email protected]] 
> Sent: Wednesday, February 27, 2013 4:26 PM
> To: dev
> Subject: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
> 
> Hi folks,
> 
> Now that we've got a 2.x version of bndlib in Maven Central 
> (http://search.maven.org/#artifactdetails%7Cbiz.aQute%7Cbndlib%7C2.0.0.20130123-133441%7Cjar
>  - same level as shipped in bndtools 2) I'm looking to sort out a new release 
> of the maven-bundle-plugin, once I've gone through and triaged the pending 
> issues in JIRA.
> 
> I also figure that now might be the best time to "fix" the plugin name 
> according to Maven guidelines: 
> http://maven.apache.org/guides/development/guide-plugin-documentation.html - 
> apparently the name "maven-NNN-plugin" is supposed to be reserved for plugins 
> hosted by Apache Maven, while plugins hosted elsewhere should use names like 
> "NNN-maven-plugin".
> 
> So along with the upgrade to bndlib 2.x, I'm proposing to change the plugin 
> name to:
> 
>       bnd-maven-plugin
> 
> which both respects the Maven plugin naming convention, and recognises the 
> bnd code which is actually doing most of the work.
> 
> WDYT?
> 
> --
> Cheers, Stuart
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to