One solution is simple: create a Maven meta-project:
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>com.agipi</groupId>
<artifactId>metaproject-extranet</artifactId>
<packaging>pom</packaging>
<version>1.0.0</version>
<modules>
<module>../project1</module>
<module>../project2</module>
[...]
<module>../project10</module>
</modules>
</project>
- Calling "mvn clean" on this meta-project cleans all modules
- Calling "mvn package" on this meta-project calls "mvn package" on all
specified modules, and in the correct dependency order, regardless of the
order in which the modules are declared in the meta-project/pom.xml (which
is very nice)
--
View this message in context:
http://www.nabble.com/automatically-calling-%22install%22-target-for-projects-which-are-not-in-the-repository-tp23403861p23426642.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
