You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mark_E <ma...@trustvesta.com> on 2007/10/15 21:10:16 UTC
Jar Version Best Practice
Hello,
I have been using Maven for about a month now and I really like it
however, I am having an issue with setting jar versions and I was looking
for suggestions on how other people do it.
I basically have a pom for each project I build. In the pom.xml I have the
dependencies. We typically version jars here with a 4 digit number so they
change each build, unlike say 1.1-SNAPSHOT.
So that I do not have to set the dependency versions in each POM, I listed
all the versions of the jars in the settings.xml. This has been working good
such that I only have to set the version in 1 spot when I do a build
Where I run into problems is when I try to build a jar that depends on one I
just build and installed in maven. What happens is it gets the pom.xml for
that jar I just built and because the pom.xml has variables assigned to the
version (which are defined in the settings.xml) I gets confused and says it
cannot find the jar version. It does not resolve the variable.
If after I build a jar, I go and delete the pom that it adds to the
repository then I try to build another jar that depends on that jar I just
built, it build fine.
Log story short, I probably have the jar versions in the wrong place. I
figure they should go in a parent pom but with the parent pom, I have to add
it to maven after each update. I suppose I could do that with a simple
script but I was just looking for input on how others do this.
Besides that issue, I have been using Maven 2.0 and testing Continuum with
it and it seems to work well.
Thanks in advance!
Regards,
Mark
--
View this message in context: http://www.nabble.com/Jar-Version-Best-Practice-tf4629682s177.html#a13219663
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jar Version Best Practice
Posted by Mark_E <ma...@trustvesta.com>.
Hello Wayne,
Thanks for the information. I will take a look at that plugin.
Regards,
Mark
Wayne Fay wrote:
>
> The release plugin solves most people's version issues.
>
> Wayne
>
> On 10/15/07, Mark_E <ma...@trustvesta.com> wrote:
>>
>> Hello,
>> I have been using Maven for about a month now and I really like it
>> however, I am having an issue with setting jar versions and I was looking
>> for suggestions on how other people do it.
>>
>> I basically have a pom for each project I build. In the pom.xml I have
>> the
>> dependencies. We typically version jars here with a 4 digit number so
>> they
>> change each build, unlike say 1.1-SNAPSHOT.
>>
>> So that I do not have to set the dependency versions in each POM, I
>> listed
>> all the versions of the jars in the settings.xml. This has been working
>> good
>> such that I only have to set the version in 1 spot when I do a build
>>
>> Where I run into problems is when I try to build a jar that depends on
>> one I
>> just build and installed in maven. What happens is it gets the pom.xml
>> for
>> that jar I just built and because the pom.xml has variables assigned to
>> the
>> version (which are defined in the settings.xml) I gets confused and says
>> it
>> cannot find the jar version. It does not resolve the variable.
>>
>> If after I build a jar, I go and delete the pom that it adds to the
>> repository then I try to build another jar that depends on that jar I
>> just
>> built, it build fine.
>>
>> Log story short, I probably have the jar versions in the wrong place. I
>> figure they should go in a parent pom but with the parent pom, I have to
>> add
>> it to maven after each update. I suppose I could do that with a simple
>> script but I was just looking for input on how others do this.
>>
>> Besides that issue, I have been using Maven 2.0 and testing Continuum
>> with
>> it and it seems to work well.
>>
>> Thanks in advance!
>>
>> Regards,
>> Mark
>> --
>> View this message in context:
>> http://www.nabble.com/Jar-Version-Best-Practice-tf4629682s177.html#a13219663
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Jar-Version-Best-Practice-tf4629682s177.html#a13220093
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jar Version Best Practice
Posted by Wayne Fay <wa...@gmail.com>.
The release plugin solves most people's version issues.
Wayne
On 10/15/07, Mark_E <ma...@trustvesta.com> wrote:
>
> Hello,
> I have been using Maven for about a month now and I really like it
> however, I am having an issue with setting jar versions and I was looking
> for suggestions on how other people do it.
>
> I basically have a pom for each project I build. In the pom.xml I have the
> dependencies. We typically version jars here with a 4 digit number so they
> change each build, unlike say 1.1-SNAPSHOT.
>
> So that I do not have to set the dependency versions in each POM, I listed
> all the versions of the jars in the settings.xml. This has been working good
> such that I only have to set the version in 1 spot when I do a build
>
> Where I run into problems is when I try to build a jar that depends on one I
> just build and installed in maven. What happens is it gets the pom.xml for
> that jar I just built and because the pom.xml has variables assigned to the
> version (which are defined in the settings.xml) I gets confused and says it
> cannot find the jar version. It does not resolve the variable.
>
> If after I build a jar, I go and delete the pom that it adds to the
> repository then I try to build another jar that depends on that jar I just
> built, it build fine.
>
> Log story short, I probably have the jar versions in the wrong place. I
> figure they should go in a parent pom but with the parent pom, I have to add
> it to maven after each update. I suppose I could do that with a simple
> script but I was just looking for input on how others do this.
>
> Besides that issue, I have been using Maven 2.0 and testing Continuum with
> it and it seems to work well.
>
> Thanks in advance!
>
> Regards,
> Mark
> --
> View this message in context: http://www.nabble.com/Jar-Version-Best-Practice-tf4629682s177.html#a13219663
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org