Matt, On Thu, 02 Sep 2004 09:41:51 -0400, Matt Coarr <[EMAIL PROTECTED]> wrote:
> If you want to do this you can create another maven project and have > your war project include that as a dependency. The multiproject plugin > ties all this together nicely. Yes, I know. But as I mentioned earlier, this is an overkill for this situation. > This fits with the one-artifact-one-project guideline. Each project (or > sub-project) should only create one jar/ear/war file. The one-artifact-one-project doesn't apply always, specially when you're a developing components. I think there are situations where your project deploys a main artifact and many secondary ones.Take for instance the javadoc.jar artifact (created by 'maven javadoc:install and other tags). If you have a component packed in a JAR, you might want to distribute the javadoc as well, so your project in fact produces 2 artifacts, the XXX.jar and XXXX-javadoc.jar. The same situation applies to some WAR projects. I might have a component that generates an auto-suficient WAR, but my customers could opt for using their own WAR, so they only need my component's jar and maybe a couple of JSP pages and/or property bundles. Besides, I think it's a good practice to encapsulate all classes in a web-app in jars, leabing the classes directory only for resources such as properties and i18n bundles. > We have had very good luck with this process. My group uses maven to > build some internal web applications. This has really cleaned up our > build process. Yes, I agree this process is better suitable for most of the web applications. But for situations like that I described above, we should let the final user to decide which approach to take (as setting a multi-project just in this case is really an overhead). Anyway, I think that discussion should be moved to the devs list and/or Jira. -- Felipe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
