:-) Not sure about Ivy, but I imagine you could definitely duplicate this functionality with ant.
FWIF we use a custom extension to Spring's TileConfigurer to do our wildcard inclusions so they can be configured in a spring applicationContext. This allows us to share common tiles definitions across multiple sites and then extend them on a site-by-site basis. It works very nicely. Rick On 10/23/09 10:32 AM, "Antonio Petrelli" <[email protected]> wrote: > 2009/10/23 Rick Mangi <[email protected]>: >> Correct. The war overlay just copies the files from an external war >> dependency into your local webapp at assembly time, so all of your tiles >> defs and jsp fragments wind up in your war file's webapp directory. We use a >> convention that tiles defs all go in WEB-INF/tiles-defs/ and then we pull >> them all in with a wildcard. Some are from our webapp, some from an included >> war. > > However I doubt that war overlays are available in Ivy, so it's time > to change to Maven :-D > > Antonio
