[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7085) AS provided classpath contains doubled entries

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-7085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561244#action_12561244 ] 

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). 

> AS provided classpath contains doubled entries
> ----------------------------------------------
>
>                 Key: JBIDE-7085
>                 URL: https://jira.jboss.org/browse/JBIDE-7085
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.M2
>            Reporter: Lukas Jungmann
>            Assignee: Rob Stryker
>             Fix For: 3.2.0.Beta2
>
>         Attachments: screenshot.png
>
>
> -create new dynamic web project with target server set to some JBossAS
> -expand runtime node in a webapp
> => see attached screenshot - runtime's classpath contains duplicated entries - for example antlr.jar from $AS/client and $AS/common/lib - only one jar should be included instead

-- 
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