I've set this up using ANT/Ivy by implementing a "buildDependencies.xml" that is run before development begins. The developer is expected to have the common project already in their environment before running the script. It copies the common assembly instructions and common jsp files from common, then runs ivy to bring in the jar dependencies. Something else I've done in the past, but haven't implemented it here yet is to wrap the CVS command line call in Java to check out the common project, and have ant call that before copying the dependencies. This way, all the developer has to do after checking their project out of the repository is remember to run the buildDependencies script.
Regards, Brian Stewart -----Original Message----- From: Rick Mangi [mailto:[email protected]] Sent: Monday, November 16, 2009 4:17 PM To: [email protected] Subject: Re: Tiles Definition Files From a Jar or War 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 >> >> This message is confidential, intended only for the named recipient and may contain information that is privileged or exempt from disclosure under applicable law. If you are not the intended recipient, you are notified that the dissemination, distribution or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient, please notify the sender at the email address listed above.
