You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Stuart McCulloch <mc...@gmail.com> on 2014/06/27 00:31:57 UTC

[ANN] Felix maven-bundle-plugin version 2.5.0 released

The Apache Felix team is pleased to announce the release of maven-bundle-plugin 2.5.0 which uses the latest release of bnd that supports Java 8 bytecode.

This is a plugin for building OSGi bundles in Maven 3 (and Maven 2) by using the bnd library from Peter Kriens:

 http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html

 http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.5.0/doc/site/index.html

 http://www.aqute.biz/Bnd/Bnd

 https://github.com/bndtools/bnd

This release is available from http://felix.apache.org/site/downloads.cgi and Maven:

 <plugin>
   <groupId>org.apache.felix</groupId>
   <artifactId>maven-bundle-plugin</artifactId>
   <version>2.5.0</version>
   <extensions>true</extensions>
 </plugin>

Release Notes:

** Improvement
   * [FELIX-3381] - Support for {maven-test-resources} and {maven-test-sources} placeholders
   * [FELIX-4205] - "null" Bundle-Activator causes bundle to fail
   * [FELIX-4518] - Provide a way to disable some plugins
   * [FELIX-4539] - Update to Bndlib 2.3.0

** New Feature
   * [FELIX-3462] - Nicer Manifest formatting
   * [FELIX-4512] - Add a new Mojo to invoke the BND Baseline tool
   * [FELIX-4517] - Generate generic capabilities and requirements for services from blueprint and scr descriptors

Enjoy!

-The Felix team

Re: [ANN] Felix maven-bundle-plugin version 2.5.0 released

Posted by Stuart McCulloch <mc...@gmail.com>.
On 27 Jun 2014 01:18, "Mark Derricutt" <ma...@talios.com> wrote:
>
> On 27 Jun 2014, at 10:31, Stuart McCulloch wrote:
>
>> This is a plugin for building OSGi bundles in Maven 3 (and Maven 2) by
using the bnd library from Peter Kriens:
>>
>> http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
>
>
> +1
>
> I see this page still points to 2.37 for the maven site

Sorry, copy-paste error - that's the old pre-CMS site. Here's the correct
link:

http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html

> rather than
>
>
http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.5.0/doc/site/index.html
>
>
>>   * [FELIX-4512] - Add a new Mojo to invoke the BND Baseline tool
>
>
> I just noticed in the new site docs theres no mention of this mojo?

There is basic (generated) mojo info:

http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.5.0/doc/site/baseline-mojo.html

For detailed usage either Simone will write something up or I'll cobble it
together from the description and examples in the JIRA issue.

>
> Mark

Re: [ANN] Felix maven-bundle-plugin version 2.5.0 released

Posted by Mark Derricutt <ma...@talios.com>.
On 27 Jun 2014, at 10:31, Stuart McCulloch wrote:

> This is a plugin for building OSGi bundles in Maven 3 (and Maven 2) by 
> using the bnd library from Peter Kriens:
>
> http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html

+1

I see this page still points to 2.37 for the maven site rather than

http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.5.0/doc/site/index.html

>   * [FELIX-4512] - Add a new Mojo to invoke the BND Baseline tool

I just noticed in the new site docs theres no mention of this mojo?

Mark

Re: [ANN] Felix maven-bundle-plugin version 2.5.0 released

Posted by Mark Derricutt <ma...@talios.com>.
On 27 Jun 2014, at 10:31, Stuart McCulloch wrote:

> The Apache Felix team is pleased to announce the release of 
> maven-bundle-plugin 2.5.0 which uses the latest release of bnd that 
> supports Java 8 bytecode.

Interesting - I just tried this on one of our other bundles and get the 
following:

[ERROR] Bundle smx3:smx3.partyresource:bundle:10.2.6-SNAPSHOT : The 
default package '.' is not permitted by the Import-Package syntax.
  This can be caused by compile errors in Eclipse because Eclipse 
creates
valid class files regardless of compile errors.
The following package(s) import from the default package null

which works fine under 2.4.0, running with -X I see the manifest as not 
including any . packages anywhere.

The last line in that output is interesting as well:

   The following package(s) import from the default package null

null?

It looks like some of our other packages however DO have a "*" import, 
which I suspect might be triggering this - time to try an epic rebuild 
under 2.5.0 :)

Mark