[
https://issues.jboss.org/browse/JBDS-1810?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1810:
----------------------------------
Here's what I've done today and am testing locally:
1. site/site.xml
{code}
<!-- OLD JBT feature has been replaced by
Eclipse.org version
<feature url="features/org.jboss.tools.bpel.feature_0.0.0.jar"
id="org.jboss.tools.bpel.feature" version="0.0.0">
<category name="JBoss Tools bpel Nightly Build Update Site"/>
</feature>
-->
<feature url="features/org.eclipse.bpel.feature_0.0.0.jar"
id="org.eclipse.bpel.feature" version="0.0.0">
<category name="JBoss Tools bpel Nightly Build Update Site"/>
</feature>
<feature
url="features/org.eclipse.bpel.apache.ode.runtime.feature_0.0.0.jar"
id="org.eclipse.bpel.apache.ode.runtime.feature" version="0.0.0">
<category name="JBoss Tools bpel Nightly Build Update Site"/>
</feature>
<!-- TODO: COMING SOON (if necessary?)
<feature url="features/org.jboss.tools.bpel.runtime.feature_0.0.0.jar"
id="org.jboss.tools.bpel.runtime.feature" version="0.0.0">
<category name="JBoss Tools bpel Nightly Build Update Site"/>
</feature>
-->
<feature url="features/org.jboss.tools.bpel.test.feature_0.0.0.jar"
id="org.jboss.tools.bpel.test.feature" version="0.0.0">
<category name="JBoss Tools bpel Nightly Build Update Site"/>
</feature>
{code}
(Test feature will not be published to JBT aggregate, it's just there so we can have a
bot tests site for QE to use.)
2. site/pom.xml will resolve from
https://hudson.eclipse.org/hudson/job/bpel-0.5/lastSuccessfulBuild/artifa...
with
http://download.eclipse.org/bpel/update-site/ as backup source in case Hudson's
down
3. {plugins/pom.xml} will now only build {org.jboss.tools.bpel.runtimes}
Note that the local test will attempt to build the current copy of
org.jboss.tools.bpel.runtimes, not the version in bbrodt's workspace.
Push BPEL editor development back upstream to
eclipse.org
---------------------------------------------------------
Key: JBDS-1810
URL:
https://issues.jboss.org/browse/JBDS-1810
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: integration, SOA Platform
Reporter: Robert (Bob) Brodt
Assignee: Robert (Bob) Brodt
Fix For: 5.0.0.M4
The BPEL editor development will be moved back to
eclipse.org - JBT/JBDS and SOA builds
should include the plugins from the eclipse update site at
http://download.eclipse.org/bpel/update-site/
Most of the bundle ids will be the same except for the cheatsheet plugin which will be
moving to
eclipse.org and will be renamed from org.jboss.tools.bpel.cheatsheet to
org.eclipse.bpel.cheatsheet. I was planing on renaming the JBoss/Riftsaw deployment plugin
from org.jboss.tools.bpel.runtimes to org.eclipse.bpel.jboss.riftsaw.runtime (since
there's already a org.eclipse.bpel.runtimes and following in the naming pattern of
org.eclipse.bpel.apache.ode.runtime) but if we're going to keep this plugin at jboss,
it'll probably remain the same.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira