Hi folks, I've taken a closer look at the two GUMP projects running for us. Updating commons-httpclient-2.0-branch with the new source location is no problem. But the commons-httpclient project in the jakarta-commons file is a different beast. Commons subprojects are referenced as relative directories. It would not look good to hack some .. sequences in there.
So, the clean solution is: - tweak SVN so all relevant trunks, and only the trunks, are checked out into a single tree - define a new httpcomponents.xml for all our GUMP jobs - move commons-httpclient from jakarta-commons.xml there - move commons-httpclient-2.0-branch there and delete the separate definition - (later) add new projects for httpcore and httpclient I'm not in the mood to try this today. Thoughts? cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
