Well, I'm using "pom" as the packaging value now, but it isn't really what I want. I'd rather not install anything to my repository that has no value. Just don't want it cluttered up.
Is there a way to do this? I guess I could create my own plugin that does this and attach it to a packaging value of "nothing". ..David.. -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jorg Heymans Sent: Monday, October 24, 2005 9:32 AM To: [email protected] Subject: Re: [m2] Project that doesn't create a package David Jackman wrote: > It's customary to have a root pom also contain module elements > indicating the subprojects so one can build them all at once. I would > like to separate the two, so I have a root pom that produces only the > pom that others will inherit, and a separate project that defines the > module elements for building many projects at once. This "multi" > project won't need to produce any type of package, or install or > deploy anything. Is this kind of project possible? What would be the > value for packaging that I would use? IIUC, <packaging>pom</packaging> should do the trick. It will always produce "something" in the repository though, why would this be a problem? Jorg --------------------------------------------------------------------- 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]
