The warpath plugin allows WARs to act like JARs. If we didn't use it, we couldn't read classes and dependencies from WARs. We'd have to have 2 projects for each web framework if we didn't use it - one for the classes and dependencies, and one for the view/configuration files.
Matt On Fri, May 9, 2008 at 6:28 AM, icet <[EMAIL PROTECTED]> wrote: > > Hi, could someone explain to me what does the warpath plugin does that maven > already doesn't do? > > * Develop with classes included in the war artifact /WEB-INF/classes > directory by including them in the project classpath. > Why maven doesn't do this already? Wouldn't it just be the case to > rename the .war to .jar ? > > * Automatically inherit transitive dependencies from the war artifact > (the default Maven behaviour is not to inherit transitively from war > dependencies). > Can't I inherit from the war's pom to get its dependencies? > > thanks > -- > View this message in context: > http://www.nabble.com/When-should-I-use-the-warpath-plugin--tp17146883s2369p17146883.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
