[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4570) New ESB project has ... ... very odd... component xml file

[Rob Stryker (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker updated JBIDE-4570:
-------------------------------

    Attachment: JBIDE-4570.patch


here's a patch. But we still need to wait for the plugin to be added to the build

> New ESB project has ... ... very odd... component xml file
> ----------------------------------------------------------
>
>                 Key: JBIDE-4570
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4570
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.1.0.M1
>            Reporter: Rob Stryker
>            Assignee: Denny Xu
>            Priority: Critical
>             Fix For: 3.1.0.M3
>
>         Attachments: JBIDE-4570.patch
>
>
> A new ESB project has hte following inside it's component.xml file:
> 	<wb-module deploy-name="TestESB">
> 		<wb-resource deploy-path="/" source-path="/esbcontent" />
> 		<wb-resource deploy-path="/esbcontent" source-path="/src" />
> 		<property name="java-output-path" value="/build/classes/" />
> 	</wb-module>
> The question is, why is the following line in there at all?
> 		<wb-resource deploy-path="/esbcontent" source-path="/src" />
> If the Module Factory were properly made and checked the VCF for all mappings, (a goal that we have for the future), this would make all files in Project/src be published in Project.esb/esbcontent,  which is clearly incorrect.
> Do you mean that source-path /src   should be mapped to deploy-path / ?  

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