al Message-
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Monday, October 19, 2009 5:45 PM
To: users@maven.apache.org
Subject: RE: Config.jar project dependency
ok up until i saw httpa and httpb?..as enjoyable as trying to convert a 10 year
old unix makefile with no comments
how about u
ous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Mon, 19 Oct 2009 21:30:16 +0200
> Subject: Re: Config.jar project dependency
> From: and...@hammar.net
> To: users@maven.apache.org
>
> I would say that most of the time when you start thinking about
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
Behalf Of Anders Hammar
Sent: Monday, October 19, 2009 3:30 PM
To: Maven Users List
Subject: Re: Config.jar project dependency
I would say that most of the time when you start thinking about using
classifiers, you should think again. The Ja
> I believe you're with me on this but I wanted to firmly state this as there
> are some very bad examples of classifiers usage. Have a look at this and
> weep:
> http://repository.jboss.org/maven2/org/jboss/jbossas/jboss-as-varia/5.1.0.GA/
>
[silence]
I would say that most of the time when you start thinking about using
classifiers, you should think again. The Javadoc and sources cases are good
examples of when classifiers are the way to go, but I've seen some very ugly
cases where people try to go about the original issue with bad Maven design
The examples are perfect. Thanks.
> I think Todd answered your second question already. One gotcha - there's
> only one pom, so you can't have different dependencies per classified
> artifact. This can be worked around with excludes in the downstream
> project, but if you run into this repeatedly
in Beukes [mailto:quin...@skywalk.co.za]
Sent: Monday, October 19, 2009 2:48 PM
To: Maven Users List
Subject: Re: Config.jar project dependency
>> OK, firstly you can only produce one artifact per POM.
> This is not true. A POM has one GAV, but you can produce multiple
artifacts with dif
\classifer>
>
> or
>
> a.b.c
> abc
> 1.0
> jdk1.5<\classifer>
>
> ---
> Todd Thiessen
>
>
>> -Original Message-
>> From: Quintin Beukes [mailto:quin...@skywalk.co.za]
>> Sent: Monday, October 19, 2009 2:48 PM
>> To: Maven
om: Quintin Beukes [mailto:quin...@skywalk.co.za]
> Sent: Monday, October 19, 2009 2:48 PM
> To: Maven Users List
> Subject: Re: Config.jar project dependency
>
> >> OK, firstly you can only produce one artifact per POM.
> > This is not true. A POM has one GAV, but you can
>> OK, firstly you can only produce one artifact per POM.
> This is not true. A POM has one GAV, but you can produce multiple artifacts
> with different classifiers. For example, most Java projects using the release
> plugin will have a source JAR file produced from the same POM and codebase.
>
Quintin Beukes wrote:
> OK, firstly you can only produce one artifact per POM.
This is not true. A POM has one GAV, but you can produce multiple artifacts
with different classifiers. For example, most Java projects using the release
plugin will have a source JAR file produced from the same POM an
gt; |-mibs
>
> So to save my self time I used to have ant script that jared configuration
> into config.jar. Afterwords I could run application locally and also deploy
> everything to remote server.
>
> Now I'm trying to use maven as primary build tool.
>
> --
> View thi
ge in context:
http://www.nabble.com/Config.jar-project-dependency-tp25939781p25946570.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional com
;
>> PS using new project just for configuration doesn't work for me.
>>
>> Any suggestions are more then welcome. Thnx.
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Config.jar-project-dependency-tp25939781p25946335.html
>>
doesn't work for me.
>
> Any suggestions are more then welcome. Thnx.
>
> --
> View this message in context:
> http://www.nabble.com/Config.jar-project-dependency-tp25939781p25946335.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> --
oject just for configuration doesn't work for me.
Any suggestions are more then welcome. Thnx.
--
View this message in context:
http://www.nabble.com/Config.jar-project-dependency-tp25939781p25946335.html
Sent from the Maven - Users mailing list archive at
> project1
>> |-
>> |-config.jar
>>
>> lib-project2
>>
>> project1 depends on lib-project2. Lib project loads configuration from
>> classpath.
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Config.j
ar
>
> lib-project2
>
> project1 depends on lib-project2. Lib project loads configuration from
> classpath.
>
>
> --
> View this message in context:
> http://www.nabble.com/Config.jar-project-dependency-tp25939781p2
-project2
project1 depends on lib-project2. Lib project loads configuration from
classpath.
--
View this message in context:
http://www.nabble.com/Config.jar-project-dependency-tp25939781p25939781.html
Sent from the Maven - Users mailing list archive at Nabble.com
19 matches
Mail list logo
