[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12490555#action_12490555 ] 

Nick Boldt commented on JBIDE-5038:
-----------------------------------

Well, my usual explanation for "sources not found while building is:

because they're not included in the map files that PDE uses to fetch sources. When you add new plugins or features (or test plugins/features), you have to let me or Denis (or anyone with write permission to http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.releng/builders/bpel/ ) know what new stuff has been added. 

However, org.eclipse.bpel.apache.ode.deploy.model plugin is already in the map, and its build.properties looks OK (though I've added the "." entry just in case that'll help).

> With changes to BPEL project wizard, BPEL deployment is broken in UI
> --------------------------------------------------------------------
>
>                 Key: JBIDE-5038
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5038
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: bpm
>            Reporter: Brian Fitzpatrick
>            Assignee: Denny Xu
>            Priority: Critical
>             Fix For: 3.1.0.CR1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Rob helped out with getting the BPEL project structure working like the ESB project structure so we are more consistent down the line and have more flexibility. We now have a JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
> The downside to this is that we lose the Apache ODE Descriptor code that used to work (in fact, it's broken and throws an error when you try to use it or open a non-ODE deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in: org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's now not connected to our BPEL project. So we need to create a new mechanism for generating the JBoss Riftsaw deployment descriptor.

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