[
https://jira.jboss.org/jira/browse/JBIDE-2875?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-2875:
--------------------------------------------
No, if the user place it in some other folder his intention is to *not* get them
deployed.
I know you are trying to adjust for any arbitrary structure but unfortunately WTP does not
really allow for that. If users want arbitrary deployment their best choice is to use the
project Archives functionallity to define a custom deployment.
Pick up jboss-esb.xml and deployment.xml files to the correct path
when packaging a deployable archives
-------------------------------------------------------------------------------------------------------
Key: JBIDE-2875
URL:
https://jira.jboss.org/jira/browse/JBIDE-2875
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.0.0.beta1
Reporter: Denny Xu
Assignee: Denny Xu
Priority: Blocker
Fix For: 3.0.0.beta1
for now, if the user does not put the esb configuration files(such as jboss-esb.xml and
deployment.xml) into the esbcontent folder, they will not be packaged into the deployment
archive, it should be:
if there is no jboss-esb.xml and deployment.xml under the esbcontent/META-INF, check if
there is a jboss-esb.xml file in other folders of the project, if there is, then package
it into deployment archive.
--
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