[jbosstools-issues] [JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
Mickael Istria (JIRA)
jira-events at lists.jboss.org
Wed Dec 5 10:12:27 EST 2012
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739657#comment-12739657 ]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
[~elvisisking]: how do you know that it's using the suggested soa target platform? That's why I'd like you to try step 1 to 4, so we are sure you are actually testing the new SOA target-platform.
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Fix For: 4.0.x
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
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
More information about the jbosstools-issues
mailing list