First question: why do you care if the pom gets installed? Second question: are the subprojects inheriting from this pom? In other words, do they declare that pom as their parent?
If yes, then you must install/deploy this pom or maven won't be able to use the subprojects. If no, then change the dist management section in this pom to point to a folder like file:///target/garbage --Brian -----Original Message----- From: Vincent Thévenin [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2008 7:26 AM To: [email protected] Subject: Avoiding a parent project from being installed into the repository Hello, I'm using Maven 2.0.9. I have a project with the following layout: project |-- pom.xml (packaging = pom) |-- ejb_subproject | |-- pom.xml (packaging = ejb) | `-- . . . `-- ear_subproject |-- pom.xml (packaging = ear) `-- . . . The two subprojects are declared as modules of the top pom.xml. Invoking Maven on the top pom.xml first launches a build on the ejb_project (which creates two artifacts, a Jar and an EJB client Jar), then on the ear_project (which creates an Ear using the Jar of the ejb_project). My issue is that installing the artifacts into the repository by invoking 'mvn install' on the top pom.xml creates three entries in the repository, one for the ejb_subproject, one for the ear_subproject and finally one for the top pom.xml, the latter being actually empty. Is it possible to inform Maven that the pom.xml of type 'pom' should not be installed into the repository, but just exists to make an entry point for the build of the two other projects? Thanks in advance. Vincent. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
