From: <sco...@jb...> - 2005-07-12 18:50:14
|
I'm inclined to not checkin the thirdparty contents into cvs and to simply change the directions for building 4.0.3+ to include using the jboss-4.0.x cvs alias. The first dependency of the jboss-4.0/build/build.xml should be to build the thirdparty contents based on the build-thirdparty.xml. The libraries.ent file should be an artifact generated in the thirdparty directory and the scripts should be updated to use this version. The source release associated with a dist would continue to include the thirdparty contents so that its a self contained bundle. The biggest compatibility issue are the eclipse classpath entries. Someone can write another visitor that generates the project eclipse classpath when thirdparty is build instead of relying on cvs versions. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884578#3884578 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884578 |