[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-5636) Java class in ESB project does not get compiled and deployed in ESB archive

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-5636.
--------------------------------

    Resolution: Done


I've found it. It seems this was introduced when backporting from upstream WTP into our codebase. The output-folders reference was still included in the raw level, but it was not being recognized due to a poorly functioning if clause. 

This was entirely my fault, but I'm shocked it wasn't noticed. 

> Java class in ESB project does not get compiled and deployed in ESB archive
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-5636
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5636
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>         Environment: JBDS 3.0 CR1
>            Reporter: Aaron Pestel
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.1.0.CR2
>
>         Attachments: LabWebService.zip
>
>
> 1.)  Create an ESB project
> 2.)  Add a Java Action to the "src" directory
> 3.)  Add a Generic Action to the esb.xml and point it at the Java class just created
> 4.)  Add project to SOA-P 5 server
> 5.)  Notice ClassNotFound exception in server console
> If you look in the server deploy directory, their is no .class file for the .java file created in step #2

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