[
https://issues.jboss.org/browse/JBTIS-29?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBTIS-29:
---------------------------------
[~maxandersen]:
Tests and verifications were done in the three respective projects, including
[~rob.stryker]'s PR here:
https://github.com/droolsjbpm/droolsjbpm-tools/pull/18
I'm not 100% everything works correctly, but then that's most likely because all
we did was MOVE it, but not actually update the code to work w/ Kepler. [~ldimaggio] would
be able to say more on this.
{quote}
On 03/23/2013 12:35 AM, Nick Boldt wrote:
Yes. Although this PR [1] is still pending, you no longer need to
include the runtime-soa stuff in JBTIS 4.0.
[1]
https://github.com/jbosstools/jbosstools-runtime-soa/pull/11
Any idea who owns that project and can apply the PR? It'd be great to be able to
finally close JBIDE-11098.
On 03/22/2013 03:04 PM, Paul Leacu wrote:
Hey Nick -
Are we at the point where I can remove runtime-soa from the
compositeArtifacts/Content xmls
in JBTIS?
Thanks!
--paull
{quote}
Migrate runtime detection plugins for SOA Tooling to their respective
projects
------------------------------------------------------------------------------
Key: JBTIS-29
URL:
https://issues.jboss.org/browse/JBTIS-29
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: distribution, drools/ jBPM5, ESB, jBPM3, releng, runtime-soa
Affects Versions: 4.0.0
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 4.0.0
You'll no doubt want a new feature wrapper for each of these plugins, as they'll
need to be installable from their respective projects' sites:
* org.jboss.tools.runtime.drools.detector
* org.jboss.tools.runtime.esb.detector
* org.jboss.tools.runtime.jbpm.detector
--
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