Return-Path: 
 <ace-dev-return-1082-apmail-incubator-ace-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ace-dev-archive@minotaur.apache.org
Received: (qmail 8585 invoked from network); 25 Feb 2011 08:52:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 25 Feb 2011 08:52:05 -0000
Received: (qmail 69349 invoked by uid 500); 25 Feb 2011 08:52:05 -0000
Delivered-To: apmail-incubator-ace-dev-archive@incubator.apache.org
Received: (qmail 69270 invoked by uid 500); 25 Feb 2011 08:52:03 -0000
Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ace-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:ace-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:ace-dev@incubator.apache.org>
List-Id: <ace-dev.incubator.apache.org>
Reply-To: ace-dev@incubator.apache.org
Delivered-To: mailing list ace-dev@incubator.apache.org
Received: (qmail 69262 invoked by uid 99); 25 Feb 2011 08:52:02 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 08:52:02 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 08:51:59 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 9EE251B6D3C
	for <ace-dev@incubator.apache.org>; Fri, 25 Feb 2011 08:51:38 +0000 (UTC)
Date: Fri, 25 Feb 2011 08:51:38 +0000 (UTC)
From: "Geert Schuring (JIRA)" <jira@apache.org>
To: ace-dev@incubator.apache.org
Message-ID: 
 <2076089195.15639.1298623898647.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <219823025.10456.1298456078870.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (ACE-129) Use artifactId naming convention as
 used in Felix
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/ACE-129?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1299926=
7#comment-12999267 ]=20

Geert Schuring commented on ACE-129:
------------------------------------

... and yes, that means the Felix project is using its own plugin incorrect=
ly if you ask me. For instance, the site mentioned in my previous comment o=
n this issue contains the following example:

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.felix</groupId>
  <artifactId>org.apache.felix.log</artifactId>
  <packaging>bundle</packaging>
  <name>Apache Felix Log Service</name>
  <version>0.8.0-SNAPSHOT</version>
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <extensions>true</extensions>
        <configuration>
          <instructions>
            <Export-Package>org.osgi.service.log</Export-Package>
            <Private-Package>org.apache.felix.log.impl</Private-Package>
            <Bundle-SymbolicName>${pom.artifactId}</Bundle-SymbolicName>
            <Bundle-Activator>${pom.artifactId}.impl.Activator</Bundle-Acti=
vator>
            <Export-Service>org.osgi.service.log.LogService,org.osgi.servic=
e.log.LogReaderService</Export-Service>
          </instructions>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>

This may seem like a good solution, but the fact of the matter is that the =
following example would have the exact same result without breaking maven c=
onventions.

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.felix</groupId>
  <artifactId>felix.log</artifactId>
  <packaging>bundle</packaging>
  <name>Apache Felix Log Service</name>
  <version>0.8.0-SNAPSHOT</version>
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <extensions>true</extensions>
        <configuration>
          <instructions>
            <Export-Package>org.osgi.service.log</Export-Package>
            <Private-Package>org.apache.felix.log.impl</Private-Package>
            <Bundle-Activator>org.apache.felix.log.impl.Activator</Bundle-A=
ctivator>
            <Export-Service>org.osgi.service.log.LogService,org.osgi.servic=
e.log.LogReaderService</Export-Service>
          </instructions>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>


The maven bundle plugin will combine the groupId and artifactId into "org.a=
pache.felix.log" as described on http://felix.apache.org/site/apache-felix-=
maven-bundle-plugin-bnd.html

> Use artifactId naming convention as used in Felix
> -------------------------------------------------
>
>                 Key: ACE-129
>                 URL: https://issues.apache.org/jira/browse/ACE-129
>             Project: Ace
>          Issue Type: Improvement
>    Affects Versions: 0.8.0
>            Reporter: Jean-Baptiste Onofr=C3=A9
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: 0.8.0
>
>
> To be compliant with most OSGi projects, including Apache Felix, the arti=
factId of our bundles should look like:
> groupId: org.apache.ace
> artifactId: org.apache.ace.client.automation
> Like this, we will be able to directly use the artifactId in the Bundle-S=
ymbolicName of the Felix maven-bundle-plugin.

--=20
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira