On 11/06/2010 5:00 PM, Anders Hammar wrote:
Well, one way would be to use m2eclipse and have it resolve workspace
projects (default setting when importing a maven project). With automatic
build turned on, the developer doesn't have to do anything for changes in
A/B/C to take effect.
It is not clear that this is a viable way to work.
You don't want to take everyone's interim code while testing your own.
What is someone goes for lunch or needs to pee?
You want developers to work together with SNAPSHOTS so that each person
can decide when the thing that they are building is in a state for
others to build with.
It also means that a developer can set his dependencies on code that he
knows and trusts - either a release or a particular SNAPSHOT or the
latest SNAPSHOT if he/she is working closely with another developer.
Otherwise, you have no idea about what code you are building with and
you will lose a lot of time testing and searching for errors in the
wrong place.
Ron
/Anders
On Fri, Jun 11, 2010 at 22:40, Shan Syed<[email protected]> wrote:
example scenario:
- there is a super POM, which is the parent for 5 other POMs (A, B, C, D,
E), which have their own children too
- only A, B, and C are listed as modules in the super POM because the
others are logically separate (and also, issuing a build at the top with
all
the modules enabled causes out of memory issues, even when the memory
params
are set very high)
(so while all projects have the same top POM, the projects that are in D
and
E are built from those roots)
- some WAR projects in D and E have dependencies on JARs created somewhere
in A, B, and C
So! given this, a developer is actively working on one of these WAR
projects
in D or E, and also is making modifications to the code in a JAR project in
A/B/C
How can I force a rebuild of that JAR if there's a change, only through
building the WAR that's in D or E?
The developer doesn't want to have to build from the top to get A/B/C to
refresh and THEN build their WAR; they want it built automatically if there
is a change WHILE only issuing one build, on their WAR project.
I hope this makes sense - is this something I just don't understand about
maven, i.e. this is what it does? or is there a way to force ALL snapshots
dependencies to be rebuilt? Or is there some way to make sure a WAR, for
example, checks to see if it's local dependencies (i.e. JARs and things
that
inherit from the same eventual root POM) need to be rebuilt?
thanks very much
Shan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
