Sounds great Rick. I'm heading down the same path. How do you setup your development environments so that this is seamless for developers?
Ideally I'd like to be able to checkout the common project along with a site project and the merging gets handled behind the scenes (similar to how Eclipse WST dependent-module works for classes, but this creates a WEB-INF/lib/<project>.jar on publish). Rick Mangi-2 wrote: > > :-) > > 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 > > -- View this message in context: http://old.nabble.com/Tiles-Definition-Files-From-a-Jar-or-War-tp26012871p26379912.html Sent from the tiles users mailing list archive at Nabble.com.
