]
Nick Boldt commented on JBIDE-18869:
------------------------------------
We're treating Thym like a project, not like part of the TP. So it's just another
project to manage like Aerogear or Server or Base. Nothing new or hard to use.
[~gercan] just needs to remember to run the "publish my
bits to
jboss.org" job [1] whenever he wants to do a release, and the result is the parent
pom [2] will automatically pull those updated bits [3] into the build [4].
[1]
Of course we can also use the new job [1] to pull OTHER requirements into an
updates/requirements/<req-name>/<version>/ folder, if we want.
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).