This question has also arrisen recently where I work. I suggested putting
the local repository of the build machine under version control, so that it
can be rolled back to repeat any released build that we create. Hell, we'll
probably stick a copy of the jdk, ant, maven, the os, everything we can
On 17/01/07, Rupert Smith [EMAIL PROTECTED] wrote:
What about poms that use versioning syntax to specify that they can use
versions = a certain version ((e.g. [1.5,) for versions = 1.5)? My
transitive dependencies may include such a pom without me really being aware
of it. Then someone uploads
? Or did I miss something?
Gilles
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 14 January 2006 19:25
To: Maven Users List
Subject: RE: [m2] Repeatable build and plugin version resolution
I think the standard and easiest
.
Does it make sense? Or did I miss something?
Gilles
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 14 January 2006 19:25
To: Maven Users List
Subject: RE: [m2] Repeatable build and plugin version resolution
I think the standard and easiest to manage
-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 14 January 2006 19:25
To: Maven Users List
Subject: RE: [m2] Repeatable build and plugin version resolution
I think the standard and easiest to manage is to create a parent pom
that your projects inherit from. In this pom, put
something?
Gilles
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 14 January 2006 19:25
To: Maven Users List
Subject: RE: [m2] Repeatable build and plugin version resolution
I think the standard and easiest to manage is to create a parent
I think the standard and easiest to manage is to create a parent pom
that your projects inherit from. In this pom, put your plugin and
dependency versions in the pluginMangement and dependencyManagement
section. Then when you don't specify the version in your child pom's the
version from the
