Hi Spencer, thank you for sharing these details. Just my two cents... Spencer Allain wrote: > > I'm not currently looking into addressing this - at least until I can > verify that making life potentially a bit more difficult for maven > deployment with multiple artifacts (i.e. jar and war both being added to > archives). > Certainly it could be a problem... on the other hand I guess - provided that publishing the war could be considered a not-so-strict requirement - the war artifact could be marked with an apposite classifier, while the jar could remain the main artifact (I suppose that should not be a real problem for maven users). Also, even restricting the hypothesis only to project deps (hence not involving deps repositories) a convention for sharing resources between war enabled projects could be a great enhancement. I imagine a war plugin that simply adds some features to the Java or Groovy one, /letting unchanged their original output and logic/ adding only other output, conventions and logic, i.e. accessing the /webAppDir/ of relevant war projects to merge that resources with the current project ones, interpreting their deps with the right semantic (propagating provided deps the right way) and so on.
Cheers Davide -- View this message in context: http://gradle.1045684.n5.nabble.com/War-plugin-evolution-and-overlays-tp4864964p4868012.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
