You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jared Richardson <Ja...@sas.com> on 2005/02/24 15:29:05 UTC
Incremental builds/service packs
Here's another new user question.
Suppose I have N products where project X imports jars from project A, B and C. C imports from D and E, and so on. Then changes are made to project E and B.
Does Maven have any strategy or process for creating a "service pack" for product X that only includes the changed jars?
I don't see the need to go lower than the jar level because signed jars can't be patched.
Thanks in advance...
-----------------------------------------
Jared Richardson
Jared.Richardson@sas.com
919-531-9136
http://www.sas.com <http://www.sas.com/>
SAS... The Power to Know(r)
-----------------------------------------
"The plan is nothing; the planning is everything."
Dwight Eisenhower
RE: Incremental builds/service packs
Posted by Eric Pugh <ep...@upstate.com>.
Unfortunantly no.. You could do something by tracking the dependencies
in some sort of database and tracking the changes. Right now project A
has no concept that the project C depends on project E. When you update
E, you'll still have to bump the version information in project C, as
well as bumping the project info in project A.
Just to whet your appetite, Maven will at somepoint support Transitive
Dependencies where if X imports C, then it will also import D and E as
well. Some of the fallout of that might be what you need?
I also wrote a crummy (never finished) plugin called "latestversion"
that dealt with this sorta. Basically it checked if there was a newer
version of a jar available on any of the repostiroes and then spit out a
message. Something like this might help you keep up with the treadmill
of upgrades?
Out of curiosity, from your posts both here and elsewhere, it sounds
like you have massive numbers of jars to deal with. This may be off
topic, but have you looked at tools like Gump (http://gump.apache.org)?
Part of your issue I am guessing is that as your dependencies change,
the dependees start failing/not compiling. For most projects
maintaining dependencies can be done manually/ad hoc. But, for massive
numbers of projects, Gump may help by identifying where project A
requires C which requires E, but E is no longer API compatible.
Eric
-----Original Message-----
From: Jared Richardson [mailto:Jared.Richardson@sas.com]
Sent: Thursday, February 24, 2005 9:29 AM
To: Maven Users List
Subject: Incremental builds/service packs
Here's another new user question.
Suppose I have N products where project X imports jars from project A, B
and C. C imports from D and E, and so on. Then changes are made to
project E and B.
Does Maven have any strategy or process for creating a "service pack"
for product X that only includes the changed jars?
I don't see the need to go lower than the jar level because signed jars
can't be patched.
Thanks in advance...
-----------------------------------------
Jared Richardson
Jared.Richardson@sas.com
919-531-9136
http://www.sas.com <http://www.sas.com/>
SAS... The Power to Know(r)
-----------------------------------------
"The plan is nothing; the planning is everything."
Dwight Eisenhower
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org