[jbosstools-issues] [JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036539#comment-13036539 ] 

Nick Boldt commented on JBIDE-18869:
------------------------------------

OK, let me know when this latest 0.1.x is out and I'll do the same setup for Thym in 4.2.x as in master. Will you run the requirement job [0] so that the new Thym appears here [1]?

[0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-requirements/
[1] http://downloads.jboss.org/jbosstools/updates/integration/luna/core/thym/


> migrate Thym from TP to being an aggregated component
> -----------------------------------------------------
>
>                 Key: JBIDE-18869
>                 URL: https://issues.jboss.org/browse/JBIDE-18869
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: aerogear-hybrid, build, target-platform, updatesite
>    Affects Versions: 4.2.0.Final
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
>
> Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP.
> This would allow it to be incorporated into builds more easily and would avoid TP churn.
> This should be fixed in master then backported for 4.2.2 (or 4.2.3).



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)