[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:comment-tabpanel&focusedCommentId=12975333#comment-12975333 ] 

Paul Leacu commented on JBTIS-282:
----------------------------------

Sounds good - I'll use Nick's script to generate the JBTIS TP which pulls in JBT core dependencies.  This will save time and be less error prone.  There are still publishing steps that must be done to [1] and [2] before the component poms can see it.

[1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/targetplatforms/jbtistarget/luna
[2] https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform

FYI:
The JBoss Tools Integration Stack Target Platform project creates two target files:

An aggregate of the JBoss Tools Core target dependencies + Integration Stack base target dependencies (base).
      e.g.  http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.8.Final/aggregate-base.target

An aggregate of the JBoss Tools Core target dependencies + Integration Stack base target dependencies + any other community dependencies (full).
     e.g.  http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.8.Final/aggregate-full.target

The JBoss Tools Integration Stack Target Platform project also creates one repository:
     e.g.  http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Alpha4/REPO/

The integration-stack base target dependencies are deployed to the JBoss nexus releases repository for use by the integration stack component projects.
     e.g.  https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.1.8.Final/

Target artifacts local to the IS:
    integration-stack-base.target - integration stack component required dependencies
    core.base.target - JBoss tools core required dependencies
    community.target - dependencies specific to the community (not required for JBDS)

Target artifacts drawn from org.jboss.tools.targetplatforms:
    jbosstools-unified....target

Ultimately the target platform dependencies are merged like this:
    integration-stack specific target dependencies:     integration-stack-base.target
    JBoss Tools core target dependencies:               + core-base.target
    JBoss Tools unified core target dependencies:    + jbosstools-unified....target    =   aggregate-base.target
    community-specific target dependencies:            + community.target                  =   aggregate-full.target


> 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
>
> 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)