[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4122) Help -> Project Examples -> ESB Problems

[ https://jira.jboss.org/jira/browse/JBIDE-4122?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4122: --------------------------------------- Fix Version/s: 3.0.1.GA Description: The Target Server should be updated to the default jboss-soa-p.4.3.0. All of the available ESB projects should just work w/o any library/classpath/etc changes. There should be no warnings and no red x's in the tree view after I do an import. was: The Target Server should be updated to the default jboss-soa-p.4.3.0. All of the available ESB projects should just work w/o any library/classpath/etc changes. There should be no warnings and no red x's in the tree view after I do an import. It would be nice if the jboss-esb.xml file not in ${projectName}/esbcontent/META-INF/, it would be nicer if it was in a conf direction maybe and then during build and deployment it would be put into the right correct space. This change might also need to be done to the New ESB Project Wizard also. What is the standard in Eclipse for things like config files? Assignee: Denny Xu Priority: Blocker (was: Major) Denny, could we please get this fix ASAP ? Thanks. Jim, I removed the " It would be nice if the jboss-esb.xml file not in ${projectName}/esbcontent/META-INF/, it would be nicer if it was in a conf direction maybe and then during build and deployment it would be put into the right correct space. This change might also need to be done to the New ESB Project Wizard also. What is the standard in Eclipse for things like config files?" part since I don't understand what the problem is with the current model for you ? -- 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