[jboss-jira] [JBoss JIRA] Resolved: (GPD-199) org.jbpm.gd.jpdl plugin contains errors (possibly not up-to-date in CVS)

[Koen Aers (JIRA)]

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

Koen Aers resolved GPD-199.
---------------------------

    Resolution: Out of Date


The 3.2 branch will be discontinued in favor of 4.

> org.jbpm.gd.jpdl plugin contains errors (possibly not up-to-date in CVS)
> ------------------------------------------------------------------------
>
>                 Key: GPD-199
>                 URL: https://jira.jboss.org/jira/browse/GPD-199
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.2.0.alpha1
>            Reporter: John Ruud
>            Assignee: Koen Aers
>            Priority: Minor
>
> I have loaded the latest org.jbpm.gd.common, org.jbpm.gd.pf, and org.jbpm.gd.jpdl plugins into my Eclipse workspace, but the org.jbpm.gd.jpdl project shows up in Eclipse as containing a number of errors. 
> According to the plugin manifests the plugins are all: 3.2.0.alpha1, and I loaded them from HEAD (for example: HEAD in jbpm.3/designer/jpdl/org.jbpm.gd.jpdl) 
> One problem is that dom4j class references are not resolved (due to the dom4j jar not being included in the .classpath file), but there are several other errors as well (for example I needed to add org.eclipse.jface.text as a required bundle). 

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