Hi Alexander,
Thanks for the compliment. I currently ignore any classes starting with java.* since many of these are found on the primordial classloader (not one created by classpath helper).
Since XML conflicts is one of the key areas that I think Classpath Helper can provide a decent view into what's going on, let me look into why I did this (since I can't remember off the top of my head).
I mean, if its found in the primordial class loader then I don't have any information on it, but if you've added it via Eclipse as an explicit reference, off the top of my head there's no reason for me to restrict it (although I am).
Due to a very busy pending release at my day job, I probably won't have a chance to look into this until the end of June :-(
Bryant
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Thank you for the great tool!
Howto include the RT-JARs in the analysis of Classpath Helper?
Currently i use separate Eclipse projects where i place a copy of the RT-JARs and include the separate Project into my main project.
This helps me to find XML classes conflicts of severals Libraries with the RT-Jars.
Regards
Alexander
Hi Alexander,
Thanks for the compliment. I currently ignore any classes starting with java.* since many of these are found on the primordial classloader (not one created by classpath helper).
Since XML conflicts is one of the key areas that I think Classpath Helper can provide a decent view into what's going on, let me look into why I did this (since I can't remember off the top of my head).
I mean, if its found in the primordial class loader then I don't have any information on it, but if you've added it via Eclipse as an explicit reference, off the top of my head there's no reason for me to restrict it (although I am).
Due to a very busy pending release at my day job, I probably won't have a chance to look into this until the end of June :-(
Bryant