]
Max Rydahl Andersen commented on JBIDE-18869:
---------------------------------------------
no matter what we do - once we get near release time we should *not* have our builds
and/or TP point to a url that will get updated with content for next builds. i.e. we do
not want work in master influence maintanence. Thus somewhere in this setup must be w ay
to ensure we don't overlap content, i.e. need to to have a way to know what version
went in and not mixing of maintanence and master content.
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.2.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).