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

[Denis Golovin (JIRA)]

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

Denis Golovin edited comment on JBIDE-18869 at 1/15/15 3:29 PM:
----------------------------------------------------------------

Now we have one more task to take care about :)

What is going to happen to nightly builds? 
Having target platform p2 repository used in installation and something different in builds smells like trouble.



was (Author: dgolovin):
Now we have one more task to take care about :)

What is going to happen to nightly builds? 
Having target platform p2 used in installation and something different in builds smells like trouble.


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