versions in large multi-projects multi-modules
environment
I'm trying to go down the path of option #1 below :
* a super pom which define all dependencies, we can leave it in
SNAPSHOT state for the dev cycle
* all libraries reference this parent pom. The libraries can go
through a couple
I'm trying to go down the path of option #1 below :
* a super pom which define all dependencies, we can leave it in
SNAPSHOT state for the dev cycle
* all libraries reference this parent pom. The libraries can go
through a couple of version increments during the dev cycle.
Now I have a problem
the framework with its superpom and after
that updating the other superpom to reference the right libraries.
Hth,
Nick Stolwijk
-Original Message-
From: Guillaume Lederrey [mailto:[EMAIL PROTECTED]
Sent: Wed 1/9/2008 11:01 AM
To: Maven Users List
Subject: Re: Dependency versions in large
-Original Message-
From: Guillaume Lederrey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 09, 2008 11:57 AM
To: Maven Users List
Subject: Re: Dependency versions in large multi-projects multi-modules
environment
On 09/01/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I have to investigate
Subject: Re: Dependency versions in large multi-projects multi-modules
environment
On 09/01/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I have to investigate the migration to Maven in our organisation. We
have a pretty large software base : about 100 projects each
generating
3 to 6
On Wed, 2008-01-09 at 14:23 +0100, Guillaume Lederrey wrote:
Thanks a lot for all the feedback !
I am still not completely convinced ... see below.
On 09/01/2008, Beelen, M. - SPLXL [EMAIL PROTECTED] wrote:
Ïn my opition the cycle you mention where the snake bites it's tail can
only
On 09/01/2008, simon [EMAIL PROTECTED] wrote:
On Wed, 2008-01-09 at 14:23 +0100, Guillaume Lederrey wrote:
Thanks a lot for all the feedback !
I am still not completely convinced ... see below.
On 09/01/2008, Beelen, M. - SPLXL [EMAIL PROTECTED] wrote:
Ïn my opition the cycle you
Thanks for your answer !
I have read some documentation on using dependency range, but I havent
used it in any real world project yet. The documentation I have found
sometimes makes me think this is a work still in progress. As you seem
to be using it in real world projects, could you please
Guillaume:
At one of our clients, we had a very similar situation.
We opted to go with option #1, below.
It *is* a bit of a maintenance burden, but it's far more reliable and explicit
than any alternatives.
Barrett
::
Barrett Nuzum
Sr. Consultant
Direct: 918.640.4414
Fax: 972.789.1340
I'm afraid that solution #1 will be hard to scale ... We have releases
almost every day. Updating every other project every day doesnt seems
to be such a good idea either ...
But thanks for your feedback !
On 07/01/2008, Barrett Nuzum [EMAIL PROTECTED] wrote:
Guillaume:
At one of our clients,
2) use version ranges in the parent pom. This way, the new version of
the library is used by all projects as soon as it is available in our
central repository. Much easier to manage, but it sound a bit scary to
have it that much automated ... Other problem, we will loose build
reproducibility
11 matches
Mail list logo
