[
https://jira.jboss.org/jira/browse/JBPM-1420?page=com.atlassian.jira.plug...
]
Koen Aers commented on JBPM-1420:
---------------------------------
Let me document this problem a bit more.
In the jbpm source tree before the maven restructuring there was a file called
version.info.xml in the resources/gpd subfolder. This file contains information that is
used by the gpd. The contents of this file for the jPDL 3.2.3 release is the following
xml:
<jbpm-version-info name="jBPM jPDL 3.2.3"
namespace="urn:jbpm.org:jpdl-3.2">
<classpathentry path="jbpm-jpdl.jar" src="src" />
<classpathentry path="jbpm-identity.jar" src="src" />
<classpathentry path="lib/activation.jar" />
<classpathentry path="lib/antlr-2.7.6.jar" />
<classpathentry path="lib/asm.jar"/>
<classpathentry path="lib/bsh.jar"/>
<classpathentry path="lib/cglib.jar"/>
<classpathentry path="lib/commons-collections.jar"/>
<classpathentry path="lib/commons-logging.jar"/>
<classpathentry path="lib/dom4j.jar"/>
<classpathentry path="lib/hibernate3.jar"/>
<classpathentry path="lib/hsqldb.jar"/>
<classpathentry path="lib/jboss-j2ee.jar"/>
<classpathentry path="lib/jcr-1.0.jar"/>
<classpathentry path="lib/junit.jar"/>
<classpathentry path="lib/log4j.jar"/>
<classpathentry path="lib/mail.jar"/>
<classpathentry path="lib/servlet-api.jar"/>
<config path="config"/>
<examples path="examples" />
</jbpm-version-info>
This info is used by the New jBPM Project wizard in the GPD to create the correct
classpath container and attach the sources to the jbpm jars so that users can
'Ctrl+Click' on the jbpm classes and methods they use and be redirected to the
actual sources. The version info and the namespace info is also used when a new process
definition is created.
As it seems this file does not exist anymore in the new layout. We will have to create a
similar file somewhere in the distribution that contains this information. The GPD code
will need to be modified and adapted if this file will appear at another location in the
distribution or if the file will contain the information in a different way.
jBPM eclipse tools setup broken
-------------------------------
Key: JBPM-1420
URL:
https://jira.jboss.org/jira/browse/JBPM-1420
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Productization
Reporter: Heiko Braun
Assignee: Koen Aers
Priority: Critical
Fix For: jBPM 3.3.0 CR1
The eclipse tools require a jBPM installation (Preferences>jBPM>Runtime Locations).
This doesn't work with the new maven layout anymore.
--
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