You usually don't change versions each week. Only when you do a real
release.
Use SNAPSHOTS to control development.
Maven will look after your housekeeping for you.
If you use Maven the way that it is designed to be used, Maven is your
friend.
Otherwise Maven will fight you at every step.
If you find yourself doing something that is not easy or well
documented, you are probably off track.
Thousands of people are developing every conceivable type of Java
project with Maven everyday.
Ron
On 11/03/2011 4:28 AM, Stephen Connolly wrote:
On 11 March 2011 07:21, Jörg Schaible<[email protected]> wrote:
koxkorrita wrote:
hello
i have some project, subprojects using maven.
several of them are libs for import as dependencies into my maven
projects
and subprojects.
my problem is the next.
into my pom version i have the tipical 0.0.1-SNAPSHOT.
i heve 125 java project that i use frecuentry.
can i use one variable for setting it into one only place updating all
the
pom files?
i have use into the setting.xml fine this:
<my_projet_version>1.0</my_projet_version>
but if into my pom files i put the ${my_projet_version} variable it
doesn't sustitute the value
How can i make this?
i cannot change weeckly into the 125 pom files the version manually
Can yo help me?
You don't have to use variables at all. Please read
http://maven.apache.org/guides/introduction/introduction-to-dependency-
mechanism.html and in special the section about the dependencyManagement
tag.
Jörg,
it sounds like he's trying to substitute variables in one of the "doesn't
support variables" locations, i.e.
/project(/parent)?/(version|groupId|artifactId)
which is why I recommended v-m-p@mojo
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
