On 10/4/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > What i'm really asking is there any effective way to do this with a single > .pom file? > If i use a single .pom file, and I set <packaging>jar</packaging> in it, > when i try > to use artifact:install to install the .war file, it automatically changes > the suffix to .jar > when it deploys.
For what you are doing, yes. As long as they represent the same "thing" (ie one source tree, same identifier, just differing by type/classifier), then you can produce multiple artifacts. You produce one primary artifact (signified by packaging -> war), and then can register plugins and profiles to produce extra artifacts that are attached to the main artifact and deployed together. This is perfect for tld's. > Also, competing dep management products, such as ivy, do allow multiple > artifacts > to be specified in a single configuration file. that being said, i'd > rather use maven's > tasks if i can. Ivy doesn't build things, so this is kind of irrelevant. Maven's dependencies can obviously specify many dependencies themselves, not just one. > But having 3 pom files just to deploy a .jar, .war and > .ear is a pain, > especially for maintenence. Why do you need to deploy a JAR, WAR and EAR that are basically the same thing? I can understand wanting to make that easy, especially for quick deployment for testing. On the JAR -> WAR front, we encourage separate projects so your web code is separate from your model (shared jar) code. Maven is about making the best practices easy and the other things possible, remember. Hope this helps, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
