[ https://jira.jboss.org/browse/JBIDE-7085?page=com.atlassian.jira.plugin.s... ] Lukas Jungmann updated JBIDE-7085: ---------------------------------- Attachment: screenshot.png -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7085?page=com.atlassian.jira.plugin.s... ] Max Andersen commented on JBIDE-7085: ------------------------------------- Could we do a fix here where if classpath has same name and file is same size we skip it ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7085?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-7085: ------------------------------------ After discussions with some people who are familiar with AS classloading, I will add the jars in the following order, and I will remove the 'sort' that is going on now. <AS_HOME>common/lib <AS_HOME>/lib, <AS_HOME>/server/{config}/lib <AS_HOME>/client I will leave the jars on in this specific order, and I will remove duplicates *IFF* they have the same name and filesize. In the case of different filesizes, the duplicate jars will still be added but the toolset should compile against the same order as the server. Best solution, I'm getting to work on it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7085?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-7085: ------------------------------------ you did not get removed from the CC at all, nobody on AS team decided to respond to it so I took some time out to ask other people familiar with AS classpath, like Jim Ma in Beijing and whoever else I know. Basically, the alphabetical sorting never should have been done. It was a mistake from the start. Sorting of jars in the cpc should obviously match classloading order in the app server. And, as you suggested, if jars have the same name and filesize, the one added second should be ignored. The basic changes that were made were to add jars in the following order: <AS_HOME>common/lib, <AS_HOME>/lib, <AS_HOME>/server/{config}/lib, and <AS_HOME>client to the classpath . Also keep the deployers added even though it is in a separate classloader and most applications wouldn't be able to access the classes. (? Not sure if this is true but Jim told me and it seems reasonable). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira