We use maven with war overlays to pull in the shared definitions. The shared code is in a war file that is included as a maven dependency for our actual web projects.
On 11/16/09 5:15 PM, "JasonKissinger" <[email protected]> wrote: > > 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 >> >>
