No issue, go ahead.
Certainly since the libraries.ent is generated, there should be only one used everywhere. The only reason the xml versions were introduced was to prototype the ant 1.6 features including its import mechanism which required a different format.
Working in a branch off of head I have ported the thirdparty download to head. I am shooting for releasing this and the accompanying cruisecontrol changes early next week.
mkdir test cd test cvs co -r REPO_BRANCH_HEAD jboss-head.x cd jboss-head/build ./build.sh
When creating the module that does not include the thirdparty I followed the same naming schema as we used in 4.0. Does this still hold as adequate?
No, as there is no reason to keep jboss-head the same since this is the pure development branch. There is no reason to be able to build an old tagged release of jboss-head. Just send out a warning email to dev and ask if someone has a workspace in a state that should delay the change. The only thing I can see being an issue was needing to update thirdparty to test uncommitted changes.
The changes to head have been deployed.
Checkout to a clean directory
cvs co jboss-head
I have made an announcement on the dev list and will update the eclipse .classpath files.
Please let me know if you encounter any issues.