Well - if you're building an ear or war - what if there are stack specific property files that live inside the war AND property files that live OUTSIDE the war (say in a "config" directory that is a peer of the main server/deploy directory structure)? What if there is another process that has to run against your war artifact (which results in a different type of artifact)? Something, say, post package phase.
Why use resources when you can get the same thing from the assembly process? Also, why wouldn't you want the dev runtime env to look as close as possible to an actual deployment? -----Original Message----- From: Nick Stolwijk [mailto:[email protected]] Sent: Wednesday, April 29, 2009 4:12 PM To: Maven Users List Subject: Re: <resources> versus <assembly> Resources are included in your jar/war file, while an assembly creates a zip or tar.gz file, for example we create a tar.gz with our final war file, the configuration files for the different environments, some static resources which are deployed somewhere else and the deployment documents. So the administrators have all the files they need to deploy our application. Filtering is used inside the war file, to display the current version on a status page. Two different things. With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Wed, Apr 29, 2009 at 10:06 PM, EJ Ciramella <[email protected]> wrote: > Hello list - quick quesiton (I think) - > > When should one choose to process resources versus using an assembly > descriptor (with filtering on or off - depending on what you want)? > > > --------------------------------------------------------------------- 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]
