Check out section 8.4 "Handling Versioned Dependencies" of Erik Hatcher's Ant book. You might want refactor Roller's tools/lib directory layout and build script along those lines before you try a Greebotomy. It *might* make your job easier.
I could handle this if you'd like - as this is what I modeled struts-resume's build process from. Or you could look at it's build file. Basically, the lib directory contains a lib.properties that is loaded and determines the library locations/version numbers.
Yeah, but then I wouldn't get to play with a new OS tool ;-) I have to pick up Erik's book again, I've been too tired on the bus the last couple months...
Posted by
Lance
on March 03, 2003 at 04:28 PM CST
#
Okay, I read section 8.4, and that certainly is useful. However, it doesn't get at my real objective: to remove the dependancy jars from the Roller repository (or at least most of them). Greebo, like Maven, could be used to grab these jars at build time.
Since Roller still requires a developer to have run Ant once (to generate the ActionForms) already, I don't see this as an impediment. It'll reduce checkouts, reduce SourceForge bandwidth, and reduce the overhead on CVS updates (I often see it "hang" while checking the jars).
Additionally, this would be a good thing for those of us involved in more than one project using some of these resources (I've got copies of commons-lang et. al. scattered all around); to avoid library duplication.
We could combine this with the dependancy checking ala Hatcher - in fact this would be a good thing!
Posted by
Lance
on March 04, 2003 at 09:39 AM CST
#
Posted by Dave Johnson on March 03, 2003 at 04:15 PM CST
Website: http://www.rollerweblogger.org/page/roller #
Check out lib.properties from struts-resume for a sample: http://tinyurl.com/6lci
Posted by Matt Raible on March 03, 2003 at 04:26 PM CST
Website: http://raibledesigns.com #
Posted by Lance on March 03, 2003 at 04:28 PM CST #
Since Roller still requires a developer to have run Ant once (to generate the ActionForms) already, I don't see this as an impediment. It'll reduce checkouts, reduce SourceForge bandwidth, and reduce the overhead on CVS updates (I often see it "hang" while checking the jars).
Additionally, this would be a good thing for those of us involved in more than one project using some of these resources (I've got copies of commons-lang et. al. scattered all around); to avoid library duplication.
We could combine this with the dependancy checking ala Hatcher - in fact this would be a good thing!
Posted by Lance on March 04, 2003 at 09:39 AM CST #