You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Jeremy Hughes <hu...@apache.org> on 2010/04/06 15:41:17 UTC
Re: Exported packages and artifact id
+1 to that
On 22 March 2010 15:40, Guillaume Nodet <gn...@gmail.com> wrote:
> I think a good practice when writing bundles is to have all packages defined
> (and exported) by a bundle being with artifact id.
> I.e. if the artifactId is org.apache.aries.samples.blog.api, the package
> should be named org.apache.aries.samples.blog.api.persistence and not
> org.apache.aries.samples.blog.persistence.api.
>
> The reasons are:
> * this is the default for the maven bundle plugin recent versions (and
> will still be with the work i'm doing on using properties to configure the
> osgi metadata)
> * it helps avoiding split packages
>
> I won't change those right now, but I encourage everyone to make sure this
> guideline is followed everywhere.
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: Exported packages and artifact id
Posted by Joe Bohn <jo...@gmail.com>.
I agree and based on this recommendation I went ahead and changed the
api packages in the Blog and AriesTrader (and a few others) a week ago
or so to match the artifact id.
Joe
Jeremy Hughes wrote:
> +1 to that
>
> On 22 March 2010 15:40, Guillaume Nodet <gn...@gmail.com> wrote:
>> I think a good practice when writing bundles is to have all packages defined
>> (and exported) by a bundle being with artifact id.
>> I.e. if the artifactId is org.apache.aries.samples.blog.api, the package
>> should be named org.apache.aries.samples.blog.api.persistence and not
>> org.apache.aries.samples.blog.persistence.api.
>>
>> The reasons are:
>> * this is the default for the maven bundle plugin recent versions (and
>> will still be with the work i'm doing on using properties to configure the
>> osgi metadata)
>> * it helps avoiding split packages
>>
>> I won't change those right now, but I encourage everyone to make sure this
>> guideline is followed everywhere.
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>
--
Joe