[
https://issues.jboss.org/browse/JBDS-1879?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1879:
----------------------------------
The following features have been added to the target platform:
org.eclipse.bpel.apache.ode.runtime.feature_0.5.0.v20110915-1141-H87-CI.jar
org.eclipse.bpel.jboss.riftsaw.runtime.feature_0.5.0.v20110915-1141-H87-CI.jar
org.eclipse.bpel.feature_0.5.0.v20110915-1141-H87-CI.jar
They are also located here:
http://download.jboss.org/jbosstools/updates/requirements/bpel/0.5.0-2011...
Need to now verify that JBoss BPEL can build w/ the requirement from the TP instead of
from a <repository> reference.
Review Eclipse BPEL 0.5 for inclusion in JBT/JBDS
-------------------------------------------------
Key: JBDS-1879
URL:
https://issues.jboss.org/browse/JBDS-1879
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build
Reporter: Nick Boldt
Assignee: Len DiMaggio
Fix For: 5.0.0.M4
Because both Savara and JBoss BPEL depend on Eclipse BPEL, we need to be consistent w/
the version used.
Currently, we just source from here [1].
[1]
https://svn.jboss.org/repos/jbosstools/trunk/bpel/pom.xml
I would need to:
a) pull a mirror of BPEL @ Eclipse to here [2], like we do with Indigo, EMF, Eclipse,
SWTBOT, BIRT, etc.).
b) add it to the TP files [3] and respin them
c) have you both pull from the same version of Eclipse BPEL
[2]
http://download.jboss.org/jbosstools/updates/requirements/
[3]
https://svn.jboss.org/repos/jbosstools/trunk/build/target-platform/
Only wrinkle here is that we won't be able to respond as quickly to new BPEL
releases. We won't be pulling nightlies anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira