[
https://jira.jboss.org/jira/browse/JBIDE-4122?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4122:
--------------------------------------------
the standard is to put the files in the standard locations, i.e. META-INF/something should
be in META-INF/something relative to the root of the deployment. Actually makes a lot of
sense doesn't it ? :)
Note, esbcontent could be renamed to conf if you wish to.
Let me know what use case that is not solvable for you ?
If it is about having multiple esb.xml files (i.e. one for prod, test, dev etc.) then that
is something IDE's generally solve badly since they tend to like to have these
resources in standard locations and (enough) syntactically and semantically correct to be
able to parse them to build their internal model to help the developer with other things
than just copying the file.
Help -> Project Examples -> ESB Problems
----------------------------------------
Key: JBIDE-4122
URL:
https://jira.jboss.org/jira/browse/JBIDE-4122
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Jim Tyrrell
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?
--
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