Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of mcculls@gmail.com designates
 209.85.216.49 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=teRymoqGnKk1vd1sXsdSA9nOrsKv29IxOl6q5f0qSdag9P0VrRj1safzQvkRmqrX7X
         Gq5Hqykr6/fWLC5rNH4bf5jwDJexfsC7872lo9qjXzDGea/zkQdsjCBzqXtkY7MvHoYR
         j2mR0x3B/wSzTqMM3zgOnSann7LGNQV7DBwVA=
MIME-Version: 1.0
In-Reply-To: <BANLkTinaB=DGAtABLJauCB74EkXz-YbarA@mail.gmail.com>
References: <BANLkTinaB=DGAtABLJauCB74EkXz-YbarA@mail.gmail.com>
Date: Sun, 1 May 2011 12:52:23 +0100
Message-ID: <BANLkTi=gcwpDF3b07rnQ7HzzXVHC=j11=g@mail.gmail.com>
Subject: Re: maven-bundle-plugin and .impl and .internal packages
From: Stuart McCulloch <mcculls@gmail.com>
To: users@felix.apache.org
Content-Type: multipart/alternative; boundary=000e0cd5bbea456ab104a2358ae8

--000e0cd5bbea456ab104a2358ae8
Content-Type: text/plain; charset=ISO-8859-1

On 30 April 2011 23:47, Yuri de Wit <ydewit@gmail.com> wrote:

> I have been going in circles trying to figure out why certain packages
> weren't being exported until I noticed, after taking a look at the
> sources, that the maven-bundle-plugin seems to be skipping .impl and
> .internal packages.


That's correct - if you don't define any Export-Package then it defaults to
the local non-internal / non-impl packages, as described in the "Default
Behavior" section:

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

After I renamed my package to something else it
> worked as expected.
>
> Is this restriction imposed by the OSGi specs? Although in theory
> .impl means an internal package it is not always the case. Renaming
> the package is an option, but seems a bit invasive (specially without
> knowing a good reason for it to be the way it is). Last, is there a
> simple work around for this beyond renaming the package?
>

There is nothing in the specs that restrict implementation packages from
being exported, the bundleplugin defaults are based on user feedback
and current best-practice. But they are only defaults - if you want to
export internal packages then you can do so by explicitly setting
Export-Package (or _exportcontents if you're exporting packages from
embedded JARs, see the above link and FAQ for more details).

Though ideally you wouldn't want to export implementation packages, since
one benefit of modularity is that you can hide away internal /
implementation details and instead communicate via interfaces and services.
That way you get loose coupling, and substitutable bundles.


> -- yuri
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>

-- 
Cheers, Stuart

--000e0cd5bbea456ab104a2358ae8--