One solution is simple: create a Maven meta-project:
4.0.0
com.agipi
metaproject-extranet
pom
1.0.0
../project1
../project2
[...]
../project10
- Calling "mvn clean" on this meta-project cleans all modules
- Calling "mvn package" on this meta-project calls "mv
,
Software Developer
HireRight Estonia AS
-Original Message-
From: Blackbird [mailto:panzrku...@yahoo.fr]
Sent: Wednesday, May 06, 2009 1:23 PM
To: users@maven.apache.org
Subject: automatically calling "install" target for projects which are
not in the repository
Hi,
I have an
You can create a pom in a higher directory to include them as modules,
or use a combination of a ci server and an artifact repository to make
sure they are already build and waiting in the artifact repository.
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www
Hi,
I have an application composed of 10 Eclipse projects, which depend on each
other. One of them is a webapp and it depends on several Eclipse projects,
and some of these Eclipse projects depend on others, so the dependency tree
is quite complex.
In good-old Eclipse build, I don't have to care
