to
bump versions.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-versioning-tp5741895p5742459.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
does that just bump up the version of someDependency?
Most of the work I did previously with Maven was working with SNAPSHOTs so
after I am trying to wrap my head around the versioning management portion
of it.
Thanks!
--
View this message in context:
http://maven.40175.n5.nabble.com/
!
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-versioning-tp5741895.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
On 5/24/2012 7:39 AM, DK wrote:
Hi,
New to Maven and have a couple of questions around versioning.
Should all projects within a multi-module project have the same version?
Should all projects related to each other keep the same version number?
Any best practices on changing version numbers?
t; -Original Message-
>> From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
>> Sent: Thursday, May 24, 2012 11:38 AM
>> To: users@maven.apache.org
>> Subject: Re: Maven versioning
>>
>> We just got tired of checking out modules, updating the versions,
>&
; own versioning strategy.
>
> > -Original Message-
> > From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
> > Sent: Thursday, May 24, 2012 11:38 AM
> > To: users@maven.apache.org
> > Subject: Re: Maven versioning
> >
> > We just got tired of chec
@maven.apache.org
> Subject: Re: Maven versioning
>
> We just got tired of checking out modules, updating the versions,
> building and testing them, deploying them into production all just
> because some other module had a bug in it that needed fixing or
> required
> an enhancement.
&
ule project have the same
version?
Should all projects related to each other keep the same version
number?
Any best practices on changing version numbers?
Thanks
--
View this message in context: http://maven.40175.n5.nabble.com/Maven-
versioning-tp5709659.html
Sent from the Maven - Users mai
is time to think about breaking it up.
>
>> -Original Message-
>> From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
>> Sent: Thursday, May 24, 2012 10:44 AM
>> To: users@maven.apache.org
>> Subject: Re: Maven versioning
>>
>> We started
m: Ron Wheeler [mailto:rwhee...@artifact-software.com]
> Sent: Thursday, May 24, 2012 10:44 AM
> To: users@maven.apache.org
> Subject: Re: Maven versioning
>
> We started out with a "Yes".
> As the number of modules grew to over 70 and the reasons for new
> releases got m
ithin a multi-module project have the same version?
Should all projects related to each other keep the same version number?
Any best practices on changing version numbers?
Thanks
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-versioning-tp5709659.html
Sent from the M
On 24 May 2012, at 4:23 PM, DK wrote:
> So how does release work with SVN.
>
> If all my projects are at 1.0.0-SNAPSHOT.
> What will running the mvn release command do?
>
> Will it result in 1.0.1-SNAPSHOT?
Short answer is yes.
Long answer:
When you ask the release plugin to make a release fo
how does release work with SVN.
>
> If all my projects are at 1.0.0-SNAPSHOT.
> What will running the mvn release command do?
>
> Will it result in 1.0.1-SNAPSHOT?
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Maven-versioning-tp5709659p5709
So how does release work with SVN.
If all my projects are at 1.0.0-SNAPSHOT.
What will running the mvn release command do?
Will it result in 1.0.1-SNAPSHOT?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-versioning-tp5709659p5709665.html
Sent from the Maven - Users
On 24 May 2012, at 2:39 PM, DK wrote:
> Any best practices on changing version numbers?
The best practice is to let maven worry about all of this using the
maven-release-plugin.
The plugin turns a release into a single command "mvn release:prepare
release:perform", which becomes completely aut
lease plugin should be
your go-to option.
>
> Thanks
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Maven-versioning-tp5709659.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
context:
http://maven.40175.n5.nabble.com/Maven-versioning-tp5709659.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail
Yessir! Thank you muchly!!!
On Mar 24, 2010, at 2:22 PM, Paul Benedict wrote:
Please see here. I hope it's what you're looking for:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
Paul
On Wed, Mar 24, 2010 at 12:25 PM, Maven User 2.u...@gmail.com> wrote:
Please see here. I hope it's what you're looking for:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
Paul
On Wed, Mar 24, 2010 at 12:25 PM, Maven User wrote:
> Hi list,
>
> Does anyone know where the documentation lies for maven's versioning scheme?
>
> I rem
Hi list,
Does anyone know where the documentation lies for maven's versioning
scheme?
I remember seeing a page that explained what's acceptible (how many
digits, delimited, etc.).
Many thanks in advance!
-
To unsubscribe
Hello,
The current implementation for the versioning of poms is
..([-]|[-])
At least, that's what I found in the resources belong:
http://docs.codehaus.org/display/MAVEN/Versioning
http://docs.codehaus.org/display/MAVEN/Extending+Maven+2.0+Dependencies
Unfortunately, 3 digits isn't
cross this document:
> http://docs.codehaus.org/display/MAVEN/Versioning
> Is this the current state? If not, where can I find it?
>
> I want to release something with a version number that has no official
> release yet. How should I give it it's version number so that the final
> release wil
Do you mean that:
1.0 > 1.0-rc1
1.0.1 > 1.0
what about 1.0.rc1, is that bigger then 1.0?
regards,
Wim
2007/6/14, Jo Vandermeeren <[EMAIL PROTECTED]>:
On 6/14/07, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
>
> I want to release something with a version number that has no official
> release yet
On 6/14/07, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
I want to release something with a version number that has no official
release yet. How should I give it it's version number so that the final
release will be considered later?
For instance, currently they are at 1.0-SNAPSHOT, final version wi
I was looking for information about the version numbers that maven
understands and came across this document:
http://docs.codehaus.org/display/MAVEN/Versioning
Is this the current state? If not, where can I find it?
I want to release something with a version number that has no official
release ye
Hi,
I was looking for information about the version numbers that maven
understands and came across this document:
http://docs.codehaus.org/display/MAVEN/Versioning
Is this the current state? If not, where can I find it?
I want to release something with a version number that has no official
I face a challenge in applying the concepts of versions in our use of
Maven in combination with Subversion and was hoping someone could
give me some pointers. Today we employ a svn repo where we apply code
in trunk and at release time create a branch, which we test and
evolve to a point whe
27 matches
Mail list logo
