Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: "Mark Derricutt" <mark@talios.com>
To: dev <dev@felix.apache.org>
Subject: Re: [ANN] Felix maven-bundle-plugin version 2.5.0 released
Date: Fri, 27 Jun 2014 14:01:30 +1200
Message-ID: <25294E3D-6515-4A4B-BD01-E9ECADA09039@talios.com>
In-Reply-To: <5628396D-8E15-4E4B-B99F-D65884130EE7@gmail.com>
References: <46C16F59-CB77-419A-8368-896354AD22EC@gmail.com>
 <5628396D-8E15-4E4B-B99F-D65884130EE7@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed

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