Andrew Petro wrote:
The fundamental idea is that instead of build.properties properties naming paths to individual .jars and hard-coded logic in build.xml to treat these .jars differently, such that to add a .jar you've gotta update build.properties and build.xml, there are instead (optionally configurable) magic directories. The build process discovers .jars in these directories and treats them according to the properties of the directory they're in. To add a .jar to the build, simply drop it into the /lib/compile directory. To instruct the build to include a .jar at compile time but not deploy it with uPortal because you believe your container will provide it, stick it in /lib/provided . Etc.
This seems reasonable to me. I like the idea of naming the jar directories after Maven 2 names for scopes - "provided", "compile", "test", etc.
Elliot -- Join your friends and colleagues at JA-SIG with Altitude: June 24-27, 2007 in Denver, CO USA. Featuring keynotes by: Phil Windley, Matt Raible, Matt Asay Sessions on topics including: CAS, uPortal, Portlets, Sakai, Identity Management, and Open Source For more information & registration visit: http://www.ja-sig.org/conferences/07summer/index.html --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
