[
https://issues.jboss.org/browse/JBTIS-8?page=com.atlassian.jira.plugin.sy...
]
Paul Leacu commented on JBTIS-8:
--------------------------------
Paul,
1. Following features and plugins all all included in one update site
*** Features
org.guvnor.tools.feature_5.3.5.Final.jar
org.drools.eclipse.feature_5.3.5.Final.jar
org.jbpm.eclipse.feature_5.3.5.Final.jar
org.jbpm.eclipse.task.feature_5.3.5.Final.jar
*** Plugins
org.guvnor.eclipse.webdav_5.3.5.Final.jar
org.guvnor.tools_5.3.5.Final.jar
org.drools.eclipse_5.3.5.Final.jar
org.jbpm.eclipse_5.3.5.Final.jar
org.jbpm.eclipse.task_5.3.5.Final.jar
2. Latest release droolsjbpm 5.5.0.Final
https://repository.jboss.org/nexus/content/groups/public-jboss/org/drools...
3. Snapshot releases for 6.0
https://repository.jboss.org/nexus/content/groups/public-jboss/org/drools...
There are some other plugins related to jBPM and Drools as well:
The following features / plugins are related to jBPM3. Has the decision
been made that they will be included in the aggregated update site? As
I think it might be that we will no longer include these for JBDS6.
Features
org.jboss.tools.jbpm3.feature_4.5.0.Beta2-v20121106-1148-B1927.jar
org.jboss.tools.jbpm.common.feature_4.5.0.Beta2-v20121106-1148-B1927.jar
org.jboss.tools.jbpm.convert.feature_4.5.0.Beta2-v20121106-1148-B1927.jar
org.jbpm.gd.jpdl.feature_4.5.0.Beta2-v20121106-1148-B1927.jar
Plugins
org.jbpm.gd.jpdl_4.5.0.Beta2-v20121106-1148-B1927.jar
org.jboss.tools.jbpm.common_4.5.0.Beta2-v20121106-1148-B1927.jar
org.jboss.tools.jbpm.convert_4.5.0.Beta2-v20121106-1148-B1927.jar
The following features / plugins are extensions to the first set of
droolsjbpm tools, responsible for detecting a drools or jbpm runtime for
specific platforms. They were created / maintained by the JBT / JBDS
teams however.
Features
org.jboss.tools.runtime.drools.detector.feature_1.4.0.Beta2-v20121221-1759-B60.jar
org.jboss.tools.runtime.jbpm.detector.feature_1.4.0.Beta2-v20121221-1759-B60.jar
Plugins
org.jboss.tools.runtime.drools.detector_1.4.0.Beta2-v20121221-1759-B60.jar
org.jboss.tools.runtime.jbpm.detector_1.4.0.Beta2-v20121221-1759-B60.jar
Kris
On 01/07/2013 06:33 PM, Paul Leacu wrote:
Hey -
I've been working with Rob C to produce an aggregate/composite update site
project for the layered release of the JBoss tools integration stack. The good news is
that we've made sufficient progress that we need to know the particulars in more
detail. You're receiving this email because I believe that you can provide some
portion of the specifics I need. The aggregated IS capture is 162 plugins - could you
please review the attached features and plugins file and...
1. Identify which features/plugins you are responsible for (or which most closely
'belong' to you).
2. Specify the location of the most recent stable update site/repository.
3. Identify the full version of the lates release of your plugins.
I'll update the target dependencies, composite and site files and see if we can
produce an independent layered IS release!
Thanks in advance!
--paull
JBossTools Integration Stack :: drools: Verify the component
configuration of the initial IS tooling release.
-------------------------------------------------------------------------------------------------------------
Key: JBTIS-8
URL:
https://issues.jboss.org/browse/JBTIS-8
Project: JBoss Tools Integration Stack
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: drools
Environment: JBT 4.0
Reporter: Paul Leacu
Assignee: Kris Verlaenen
Please verify your component configuration of the JBoss Integration Stack for a JBoss
Tools 4.0 target.
Also check that all components are compatible with the upstream components defined in the
target platform.
ref:
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
- compositeContent.xml
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
I'm working on getting this project promoted to jbosstools in github. Unitl then
please refer to/fork the urls above. There is a best-guess already specified for each
component.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira