[esb-issues] [JBoss JIRA] Commented: (JBESB-2972) Extend locations for loading jars in as5 deployments

[Denny Xu (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12495155#action_12495155 ] 

Denny Xu commented on JBESB-2972:
---------------------------------

the early SOA-P version put all these jars in "jbossesb.sar/lib" and jbossesb.esb foldes, and JBDS adds all runtime jars there  to ESB project CLASSPATH, but in SOA-P 5.0, most of jars , such as "jbossesb-rosetta.jar", are moved to "deployers/esb.deployer/lib"  and current JBDS can not set up ESB project classpath correctly. So if this ESB runtime structure is the final structure, I have to change the way to pick up jars for ESB project classpath in JBDS.

> Extend locations for loading jars in as5 deployments
> ----------------------------------------------------
>
>                 Key: JBESB-2972
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2972
>             Project: JBoss ESB
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Deployment
>    Affects Versions: 4.7
>            Reporter: Aaron Pestel
>
> It appears that the default folder in .esb archives for picking up dependent jars has changed from "lib" to "jars".  This is does not map to the default JBDS ESB project which creates a "lib" directory and will break existing deployments of .esb files that have jars in the /lib directory of the .esb archive.
> This was created as a result of:  https://jira.jboss.org/jira/browse/SOA-1588

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira