You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Henri Gomez <he...@gmail.com> on 2009/01/29 10:39:01 UTC
Re: RE : RE : maven / osgi / repositories
Good idea.
Did you have sample pom.xml for study ?
Thanks Christophe
2009/1/29 Deneux, Christophe <ch...@capgemini.com>:
> In your OSGI bundle project, you will use the maven-assembly-plugin to generate your OSGI bundle artifact (artifactId-version-classifier.jar) with:
> - configuration of the Manifest to specify specific OSGI information:
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> [...]
> <archive>
> <manifest>
> [...]
> </manifest>
> </archive>
> </configuration>
> [...]
> </plugin>
> - a classifier set in the assembly id of the assembly descriptor.
>
>
> To reference a dependence on a OSGI bundle, you should use the dependencies mechanism:
> <dependencies>
> [...]
> <dependency>
> <groupId>org.apache.ant</groupId>
> <artifactId>ant</artifactId>
> <version>1.7.1</version>
> <classifier>osgi</classifier>
> </dependency>
> [...]
> </dependencies>
>
> So you have in your repository: an artifact usable as simple library (the default artifact) and another one usable as a OSGI bundle.
> I never try a such configuration, but I imagine that it should work fine.
>
>
> _______________________________________________________________________________
> Christophe DENEUX / Capgemini Sud / Méditerranée
> Integration Architect / OW2 PEtALS Comitter
> www.capgemini.com <http://www.capgemini.com/>
> Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE
> Join the Collaborative Business Experience
> _______________________________________________________________________________
> Please consider the environment and do not print this email unless absolutely necessary. Capgemini encourages environmental awareness.
>
> ________________________________
>
> De: Henri Gomez [mailto:henri.gomez@gmail.com]
> Date: mer. 28/01/2009 18:04
> À: Maven Users List
> Objet : Re: RE : maven / osgi / repositories
>
>
>
> 2009/1/28 Deneux, Christophe <ch...@capgemini.com>:
>> Isn't the role of the "classifier" field ?
>>
>> instead of :
>>
>> <groupId>org.apache.ant</groupId>
>> <artifactId>ant</artifactId>
>> <version>1.7.1</version>
>>
>> we could use :
>>
>> <groupId>org.apache.ant</groupId>
>> <artifactId>ant</artifactId>
>> <version>1.7.1</version>
>> <classifier>osgi</classifier>
>
> Good but how do you specify such classifier in dependants projects ?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
>
>
>
>
>
> This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is
> intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to
> read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message
> in error, please notify the sender immediately and delete all copies of this message.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: RE : RE : RE : maven / osgi / repositories
Posted by Mark Struberg <st...@yahoo.de>.
Nope Christope, if you use the assembly plugin you'll usually get
[artifactId]-[version]-[assemblyId].[assemblytype]
e.g.
distribution-1.0.0-SNAPSHOT-dist-binary.zip
if I use
<id>dist-binary</id>
in src/assembly/dist-binary.xml in _addition_ to the normal build artifact.
But keep up the good discussion about OSGi.
What about the maven-osgi-plugin [1] or the even better the maven-bundle-plugin [2] the felix folks use?
Has anyone experience with one of those yet?
LieGrue,
strub
[1] http://mavenosgiplugin.berlios.de/
[2] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
--- Deneux, Christophe <ch...@capgemini.com> schrieb am Fr, 30.1.2009:
> Von: Deneux, Christophe <ch...@capgemini.com>
> Betreff: RE : RE : RE : maven / osgi / repositories
> An: "Maven Users List" <us...@maven.apache.org>, "Maven Users List" <us...@maven.apache.org>
> Datum: Freitag, 30. Januar 2009, 9:12
> Sorry, but I haven't a such POM.
>
> Moreover, I think that you should define different
> profiles: one for the standard jar (without
> maven-assembly-plugin), another for the OSGI jar (whith the
> maven-assembly-plugin). It seems to me that when using the
> maven-assembly-plugin with the goal "attach" only
> the jar generated by the maven-assembly-plugin can be
> deployed (through maven-deploy-plugin). So to be able to
> deploy the both JARs you need two profiles.
>
> _______________________________________________________________________________
> Christophe DENEUX / Capgemini Sud / Méditerranée
> Integration Architect / OW2 PEtALS Comitter
> Tel: + 33 4 93 95 55 92 / www.capgemini.com
> <http://www.capgemini.com/>
> Porte de l'Arénas - Entrée B / 455 Promenade des
> Anglais / 06200 Nice / FRANCE
> Join the Collaborative Business Experience
> _______________________________________________________________________________
> Please consider the environment and do not print this email
> unless absolutely necessary. Capgemini encourages
> environmental awareness.
>
> ________________________________
>
> De: Henri Gomez [mailto:henri.gomez@gmail.com]
> Date: jeu. 29/01/2009 10:39
> À: Maven Users List
> Objet : Re: RE : RE : maven / osgi / repositories
>
>
>
> Good idea.
>
> Did you have sample pom.xml for study ?
>
> Thanks Christophe
>
> 2009/1/29 Deneux, Christophe
> <ch...@capgemini.com>:
> > In your OSGI bundle project, you will use the
> maven-assembly-plugin to generate your OSGI bundle artifact
> (artifactId-version-classifier.jar) with:
> > - configuration of the Manifest to specify specific
> OSGI information:
> > <plugin>
> >
> <artifactId>maven-assembly-plugin</artifactId>
> > <configuration>
> > [...]
> > <archive>
> > <manifest>
> > [...]
> > </manifest>
> > </archive>
> > </configuration>
> > [...]
> > </plugin>
> > - a classifier set in the assembly id of the
> assembly descriptor.
> >
> >
> > To reference a dependence on a OSGI bundle, you should
> use the dependencies mechanism:
> > <dependencies>
> > [...]
> > <dependency>
> >
> <groupId>org.apache.ant</groupId>
> >
> <artifactId>ant</artifactId>
> > <version>1.7.1</version>
> >
> <classifier>osgi</classifier>
> > </dependency>
> > [...]
> > </dependencies>
> >
> > So you have in your repository: an artifact usable as
> simple library (the default artifact) and another one usable
> as a OSGI bundle.
> > I never try a such configuration, but I imagine that
> it should work fine.
> >
> >
> >
> _______________________________________________________________________________
> > Christophe DENEUX / Capgemini Sud / Méditerranée
> > Integration Architect / OW2 PEtALS Comitter
> > www.capgemini.com <http://www.capgemini.com/>
> > Porte de l'Arénas - Entrée B / 455 Promenade des
> Anglais / 06200 Nice / FRANCE
> > Join the Collaborative Business Experience
> >
> _______________________________________________________________________________
> > Please consider the environment and do not print this
> email unless absolutely necessary. Capgemini encourages
> environmental awareness.
> >
> > ________________________________
> >
> > De: Henri Gomez [mailto:henri.gomez@gmail.com]
> > Date: mer. 28/01/2009 18:04
> > À: Maven Users List
> > Objet : Re: RE : maven / osgi / repositories
> >
> >
> >
> > 2009/1/28 Deneux, Christophe
> <ch...@capgemini.com>:
> >> Isn't the role of the "classifier"
> field ?
> >>
> >> instead of :
> >>
> >> <groupId>org.apache.ant</groupId>
> >> <artifactId>ant</artifactId>
> >> <version>1.7.1</version>
> >>
> >> we could use :
> >>
> >> <groupId>org.apache.ant</groupId>
> >> <artifactId>ant</artifactId>
> >> <version>1.7.1</version>
> >> <classifier>osgi</classifier>
> >
> > Good but how do you specify such classifier in
> dependants projects ?
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> users-unsubscribe@maven.apache.org
> > For additional commands, e-mail:
> users-help@maven.apache.org
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > This message contains information that may be
> privileged or confidential and is the property of the
> Capgemini Group. It is
> > intended only for the person to whom it is addressed.
> If you are not the intended recipient, you are not
> authorized to
> > read, print, retain, copy, disseminate, distribute, or
> use this message or any part thereof. If you receive this
> message
> > in error, please notify the sender immediately and
> delete all copies of this message.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail:
> users-help@maven.apache.org
>
>
>
>
>
>
>
>
>
> This message contains information that may be privileged or
> confidential and is the property of the Capgemini Group. It
> is
> intended only for the person to whom it is addressed. If
> you are not the intended recipient, you are not authorized
> to
> read, print, retain, copy, disseminate, distribute, or use
> this message or any part thereof. If you receive this
> message
> in error, please notify the sender immediately and delete
> all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE : RE : RE : maven / osgi / repositories
Posted by "Deneux, Christophe" <ch...@capgemini.com>.
Sorry, but I haven't a such POM.
Moreover, I think that you should define different profiles: one for the standard jar (without maven-assembly-plugin), another for the OSGI jar (whith the maven-assembly-plugin). It seems to me that when using the maven-assembly-plugin with the goal "attach" only the jar generated by the maven-assembly-plugin can be deployed (through maven-deploy-plugin). So to be able to deploy the both JARs you need two profiles.
_______________________________________________________________________________
Christophe DENEUX / Capgemini Sud / Méditerranée
Integration Architect / OW2 PEtALS Comitter
Tel: + 33 4 93 95 55 92 / www.capgemini.com <http://www.capgemini.com/>
Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE
Join the Collaborative Business Experience
_______________________________________________________________________________
Please consider the environment and do not print this email unless absolutely necessary. Capgemini encourages environmental awareness.
________________________________
De: Henri Gomez [mailto:henri.gomez@gmail.com]
Date: jeu. 29/01/2009 10:39
À: Maven Users List
Objet : Re: RE : RE : maven / osgi / repositories
Good idea.
Did you have sample pom.xml for study ?
Thanks Christophe
2009/1/29 Deneux, Christophe <ch...@capgemini.com>:
> In your OSGI bundle project, you will use the maven-assembly-plugin to generate your OSGI bundle artifact (artifactId-version-classifier.jar) with:
> - configuration of the Manifest to specify specific OSGI information:
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> [...]
> <archive>
> <manifest>
> [...]
> </manifest>
> </archive>
> </configuration>
> [...]
> </plugin>
> - a classifier set in the assembly id of the assembly descriptor.
>
>
> To reference a dependence on a OSGI bundle, you should use the dependencies mechanism:
> <dependencies>
> [...]
> <dependency>
> <groupId>org.apache.ant</groupId>
> <artifactId>ant</artifactId>
> <version>1.7.1</version>
> <classifier>osgi</classifier>
> </dependency>
> [...]
> </dependencies>
>
> So you have in your repository: an artifact usable as simple library (the default artifact) and another one usable as a OSGI bundle.
> I never try a such configuration, but I imagine that it should work fine.
>
>
> _______________________________________________________________________________
> Christophe DENEUX / Capgemini Sud / Méditerranée
> Integration Architect / OW2 PEtALS Comitter
> www.capgemini.com <http://www.capgemini.com/>
> Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE
> Join the Collaborative Business Experience
> _______________________________________________________________________________
> Please consider the environment and do not print this email unless absolutely necessary. Capgemini encourages environmental awareness.
>
> ________________________________
>
> De: Henri Gomez [mailto:henri.gomez@gmail.com]
> Date: mer. 28/01/2009 18:04
> À: Maven Users List
> Objet : Re: RE : maven / osgi / repositories
>
>
>
> 2009/1/28 Deneux, Christophe <ch...@capgemini.com>:
>> Isn't the role of the "classifier" field ?
>>
>> instead of :
>>
>> <groupId>org.apache.ant</groupId>
>> <artifactId>ant</artifactId>
>> <version>1.7.1</version>
>>
>> we could use :
>>
>> <groupId>org.apache.ant</groupId>
>> <artifactId>ant</artifactId>
>> <version>1.7.1</version>
>> <classifier>osgi</classifier>
>
> Good but how do you specify such classifier in dependants projects ?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
>
>
>
>
>
> This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is
> intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to
> read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message
> in error, please notify the sender immediately and delete all copies of this message.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to
read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message
in error, please notify the sender immediately and delete all copies of this message.