[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=13032600#comment-13032600 ] 

Nick Boldt edited comment on JBIDE-18869 at 1/14/15 4:19 PM:
-------------------------------------------------------------

PR [6] to set new default path for Thym mirror applied in master branch parent pom:

[6] https://github.com/jbosstools/jbosstools-build/pull/164/files

Once 4.2.2 is released, we can apply this similar change [6] into the 4.2.x parent pom. Eventually we may need a stable /mars/ site for Thym, but for now, since Thym 0.1.0 is compatible w/ both Luna and Mars, it's OK to source the same URL [3]:

[3] http://download.jboss.org/jbosstools/updates/integration/luna/core/thym/



was (Author: nickboldt):
PR to set new default path for Thym mirror applied in master branch parent pom:

https://github.com/jbosstools/jbosstools-build/pull/164/files

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