I seem to remember something that could help you that was spoken about some 
times ago.

In fact, something like -Dskip=true to avoid install or deploy.
I just crawled the archive, but couldn't find it back, maybe you'll be luckier: 
http://www.nabble.com/forum/Search.jtp?query=skip+deploy&local=y&page=1&forum=178&daterange=0

Well, maybe this one:
http://www.nabble.com/Deploying-only-some-modules-td17132557.html#a17132629

And this one too, but still unreleased (see 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-deploy-plugin/
 to be able to use the 2.4-SNAPSHOT version):
http://jira.codehaus.org/browse/MDEPLOY-63

Well, it's not totally answering your question as it's install you don't want 
to do. I don't remember about skipping install. Though imo it's not very 
important to look at your local repo, being far more important to watch out 
what you deploy on your corporate repo than the local one.

My 2 cents.
Cheers. 

-----Message d'origine-----
De : Vincent Thévenin [mailto:[EMAIL PROTECTED] 
Envoyé : lundi 23 juin 2008 13:26
À : [email protected]
Objet : 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]

Reply via email to