[jbosstools-issues] [JBoss JIRA] (JBTIS-282) JBTIS (Fuse, Teiid) need faster, more accurate, TP updates, depend on jbt

[Paul Leacu (JIRA)]

     [ https://issues.jboss.org/browse/JBTIS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Leacu resolved JBTIS-282.
------------------------------

    Fix Version/s: 4.2.0.Alpha5-TP
       Resolution: Done


The process for generating the JBTIS TP is much better now - first used to generate 4.2.0.Alpha5 TP with Nick's script.  There are still required steps to populate the various public locations - including fuse tooling whose TP is based on JBTIS TP.


> JBTIS (Fuse, Teiid) need faster, more accurate, TP updates, depend on jbt
> -------------------------------------------------------------------------
>
>                 Key: JBTIS-282
>                 URL: https://issues.jboss.org/browse/JBTIS-282
>             Project: JBoss Tools Integration Stack
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: target-platform
>            Reporter: Rob Stryker
>            Assignee: Paul Leacu
>            Priority: Critical
>             Fix For: 4.2.0.Alpha5-TP
>
>
> Several components in JBT-IS depend on components inside JBossTools.  Teiid and FuseIDE both come to mind immediately.  JBossTools updates their Target Platform very often when Eclipse is moving towards a release, and JBTIS is often left behind. 
> Keeping up to date with changes in JBossTools may be very time consuming for the JBTIS team, and I think there's a real chance to improve efficiency here by leveraging the two buildmasters ([~nickboldt] and [~mickael_istria]) on jbosstools.  The usecases may not match 100%, but I think there's a lot of possibility to save time and develop a process that works for all participants, saves time, and frees up development resources from the tedious task of keeping these target platforms merged and up to date. 
> Feedback from [~maxandersen] and [~lhein] would also be appropriate here. 



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)