Hi Brett On 8/21/05, Brett Porter (JIRA) <[EMAIL PROTECTED]> wrote: > you say you "need" to have a JAR inside WEB-INF lib instead of classes. > > We've discussed this at some length and so far there has been little evidence > this is really needed, but there have been reasons given why it is a bad idea.
I followed the discussion in the past, but I still can't really understand what are the reasons why this is such "a bad idea". I only repeatedly heard that this is "against Maven way of doing thing" and "produce two things from a project". I am still convinced that this has nothing to do with the production of two artifact: it's always a single war artifact, simply packaged in a different way. Wars can have classes unexpanded in WEB-INF/classes or jarred in WEB-INF/lib. Putting classes inside a jar doesn't mean you have to produce a standalone jar artifact (e.g. in M2 this should be done entirely by the war plugin while producing the war, not by the jar mojo) Some reason why I usually *would like* to have a war with classes packages as a jar file: - access packaging information (version etc) from manifest, you can't do that with unexpanded classes - avoid declaring tag libraries in web.xml (tld are automatically discovered only in jar files) - faster deploy if you only have to replace classes on an existing web application (without a full war redeploy) fabrizio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
