[
https://jira.jboss.org/jira/browse/JBPM-1420?page=com.atlassian.jira.plug...
]
Koen Aers commented on JBPM-1420:
---------------------------------
This config file *cannot* live in the gpd code base. This approach is the reason that we
were able to keep the GPD backward and forward compatible with all the jBPM core releases.
It is the integration point between the GPD and jBPM core and it is only a small price to
pay with respect to 'conceptual correctness'. Same reasoning for the examples. If
the examples change (for whatever reason) the changes are automatically picked up when a
user creates a jBPM project in the GPD. The existence of the version.info.xml file and the
taken approach has been discussed a lot in the early years of jBPM. It is unacceptable
that changes with this impact occur without a public discussion.
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