Well, to minimize it, you can at least use the dependencyManagement
section inside a parent pom.
Artamonov, Juri wrote:
So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT
only, because the version of the master POM is absolutely moot. If we release, we will have
to change SNAPSHOT to the next >release version (e.g. "42") in all POMs of that
are part of the release
For me this is the qestion. Let's say we released some internal libraries in
own release cycle and now I need to remember what projects uses these libraries
and change there versions for them in dependecies section MANUALLY. For example
if we used as dependency internal utils component in 50 projects then I need to
change the version 50 times!!!
Best regards,
Juri.
-----Original Message-----
From: Jorg Schaible [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 12:30 PM
To: Maven Users List
Subject: RE: Parent POM across projects
Hi Mark,
Mark Chaimungkalanont wrote on Wednesday, June 14, 2006 10:54 AM:
Jörg,
Thanks for the reply!
> So what is the difference between:
> <version>SNAPSHOT</version>
> and
> <version>latest</version>
Basically I've been naming the atlassian-base snapshots as:
1.1-SNAPSHOT
1.2-SNAPSHOT etc.
and so whenever I rev atlassian-base, I need to change all the child
projects as well. So when I release 1.3 and the latest snapshots are
now 1.3-SNAPSHOT, so I need to update all
child project pointers from 1.2-SNAPSHOT to 1.3-SNAPSHOT, which is a
slight PITA.
Specifying the parent version as:
<version>SNAPSHOT</version>
doesn't seem to pickup 1.3-SNAPSHOT (I'm assuming I need to call my
atlassian-base version, SNAPSHOT).
I did not imply this (apart from the fact that no deployed SNAPSHOT currently
works, see MNG-2289).
The key difference between "latest" and "SNAPSHOT" is that "latest"
(which doesn't work) would find out what the latest version deployed
on the repo is, and just try to use that? That way, I don't need to
update my (unreleased) child projects every time I release
atlassian-base.
The point is, that from a logical PoV there's absolutely no difference between "latest" and
"SNAPSHOT". How can you ever rebuild a released version, if "latest" is changing over time? The
whole point of "tagging" in a SCM is about reproducability. Otherwise you may already deliver the SNAPSHOT -
no difference regarding QA.
I'm thinking this *should* be a fairly common use-case, and wondered
what other solutions there are.
So either use a static version like 1.1 or bite the bullet. This is why we use SNAPSHOT
only, because the version of the master POM is absolutely moot. If we release, we will
have to change SNAPSHOT to the next release version (e.g. "42") in all POMs of
that are part of the release. You don't have to return to SNAPSHOT for those POMs though
... only if there's a need for newer global versions.
- 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
