Hi, I'm taking over the task(s) Bob described at the beginning of this post. I've identified that we need to add the following 4 new jars to the repository: . commons-io.jar . htmlunit.jar . js.jar . nekohtml.jar And we also need to upgrade commons-collections.jar and commons-httpclient.jar from version 2.1 & 2.0.2 to version 3.1 & 3.0 respectively. 3.1 commons-collections.jar and 3.0.1 commons-httpclient.jar already exist in the repository, so I modified build/build-thirdparty.xml to include them. However, this caused compile errors in multiple testsuite modules. Being new to this, I'd like to find out what is the standard procedure of handling this. Should I attempt to fix the testsuite to cope with the new version (not sure about the magnitude)? Or is it ok to include multiple versions of a jar file in the thirdparty directory (so only the admin-console's htmlunt test uses the new version, everything else remains the same)? Any other suggestions? Chi View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958630#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...