Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Mon, 17 Oct 2011 15:34:10 +0000 (UTC)
From: =?utf-8?Q?G=C3=B6kt=C3=BCrk_Gezer_=28Commented=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <58446841.704.1318865650754.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <381517581.17476.1318702511845.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DIRSERVER-1668) Making ApacheDS generate OSGI
 manifests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DIRSERVER-1668?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13128942#comment-13128942 ]=20

G=C3=B6kt=C3=BCrk Gezer commented on DIRSERVER-1668:
------------------------------------------

For all manifests, i changed OSGI manifests to some uniform model which has=
 been accepted by many OSGI based product. It has no beneficial use for me =
other than clarity, but as i see you've reasons. So i can change them back =
to a dotted notation if you wish.

shared-ldap-codec-standalone is now referenced by apacheds modules. That's =
why i had to change it too. These kind of weirdnesses will be cleaned as we=
 go through OSGI goals.
               =20
> Making ApacheDS generate OSGI manifests
> ---------------------------------------
>
>                 Key: DIRSERVER-1668
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1668
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-M4
>            Reporter: G=C3=B6kt=C3=BCrk Gezer
>              Labels: apacheds, maven-bundle-plugin, osgi
>             Fix For: 2.0.0-M4
>
>         Attachments: mvn-bnd.diff
>
>
> Current ApacheDS modules are jar files. POMs are need to be changed to ge=
nerate OSGI manifests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira