If that's true, then I probably won't bother. I'll just use a groupId for the project that isolates it from everything I'm installing that is important. Thanks for sparing me the trouble of finding this out myself.
..David.. -----Original Message----- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 25, 2005 8:54 AM To: Maven Users List Subject: Re: [m2] Project that doesn't create a package -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The part that will be tricky is having a project in the build that doesn't have anything to deliver in the install process. You'd almost need to configure the install and deploy plugins within that POM ONLY to flag them as disabled or something... Is there any reason (other than the cosmetic) why you don't want the modules listed in the root POM? One other option *might* be to write a plugin that attaches to the tail end of the build, in some late phase, that would surgically remove the module-specifying POM from the local repository. However, doing the same thing after a deployment is non-trivial, since you have to re-establish the network connection to do it. Its going to be a lot of effort, relatively speaking. At least, under the current incarnation of Maven 2. - -john David Jackman wrote: | 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: users@maven.apache.org | 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] | | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDXkcEK3h2CZwO/4URAm0sAJ9gB3kKbJiTcgV55GGQ7025XkDj5QCgq59U 2iEBvDaA1j50naV3IOeeIUs= =QyBI -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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]
