In general people seem to be moving towards not having any exploded jars in a war file... and indeed that would be the "best practice" that Maven seems to encourage.
-Stephen 2009/5/26 Stevo Slavić <ssla...@gmail.com> > Thanks Brian, unpack-dependencies does the trick, at least partially. Not > sure if it's currently best solution, to have jar's of these unpacked > dependencies excluded from the war I use maven assembly plugin. > > Wish war plugin or even dependency declaration itself would support such a > scenario, so one could configure whether dependency should be included in > the (jar, war, ...) archive in expanded form or not. Does this usage > scenario make sense to others? > > Regards, > Stevo. > > 2009/5/26 Brian Fox <bri...@infinity.nu> > > > dependency:unpack or dependency:unpack-dependencies will do this. > > > > 2009/5/19 Stevo Slavić <ssla...@gmail.com> > > > > > Hello Maven users, > > > > > > In a multimodule project, a module has war packaging and depends on > some > > of > > > the modules with jar packaging from the same project. Is there a way to > > > configure war (or some other plugin like dependency or assembly) plugin > > so > > > that war ends up with classes of other depenedant modules from the same > > > project exploded in WEB-INF/classes instead of having their jar's in > > > WEB-INF/lib? > > > > > > Regards, > > > Stevo. > > > > > >
