(I sent this last night be never showed up in my inbox, so sending it again. Sorry if you get this twice, but wanted to make sure it got out)
The commit of jmx package to HEAD to bring in JMX 1.2 from BRANCH_4_0_DR3 is done. I tagged CVS with �pre_JMX_1_2� immediately before commit and tagged with �pre_JMX_DR3� a few days ago, which is the source the committed code was based on. I tagged with �post_JMX_DR3� after all the files were committed. It looks like everything is building properly in Linux and Windows as well as starting the server with 'all' configuration is working (both Linux and Windows). I have not committed the changes for the testsuite, so it is not compiling at this point. I will be committing those files tomorrow, accompanied by another CVS tag. However, I ran the testsuite before initial commit (which will should be same results after commit) and can see the results of HEAD and the changed code at following links: before: http://e2technologies.net/projects/jboss/test/results/windows/HEAD/html/ after: http://e2technologies.net/projects/jboss/test/results/windows/rollback/html/ If you experience any problems you think are related to the checkin, please let me know. The rest of this covers the changes made... The code checked in under the jmx package was all based on the BRANCH_4_0_DR3 and had to remove some of the files at HEAD, add some files to HEAD, and modify a lot of existing files. The only package to remain untouched was the mx.loading. The packages for JMX Remoting were removed and will be added back as it�s own module (in order to break the dependency between jboss-mx and jboss-remoting). Also, if you have checked any code into the jmx module within the past couple of weeks, I can not guarantee that I did not over write the changes with my local updated copy. I tried to find any changes that I could migrate into the jmx 1.2 codebase, but is very possible I missed something. So I you have made changes to jmx, please help me by verifying that you changes made it into this commit (or are at least relevant to the new code base). Files to committed outside of jmx package: sever\src\main\org\jboss\jmx\connector\rmi\RMIConnectorImpl.java server\src\main\org\jboss\web\ WebClassLoader.java jboss.net\src\main\org\jboss\net\jmx\adaptor\server\Adaptor.java system\src\main\org\jboss\Main.java server\src\main\org\jboss\jmx\adaptor\rmi\RMIAdaptor.java tomcat\build.xml build\build.xml Had to hack in some changes to LoaderRepository. The reason is that WebClassLoader now indirectly uses this, which calls getCachedClass() at some point (per changes to HEAD at start of the month). So I copied the implementation from UnifiedLoaderRepository3 to make it work. However, this is NOT a good long term solution as LoaderRepository is an abstract class and the extending classes will need to be able to get access to the cache so it can clear it if a ClassLoader is removed. Adrian, could use your help on straightening this out. -Tom ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
