]
Nick Boldt commented on JBIDE-18869:
------------------------------------
I've updated
so that it
can now publish from any source URL (defaults to the value in [1], which is [2]) to one of
3 different destination [3] URLs [4], including the builds/staging/JOB_NAME URL [5]:
[1]
So, now all we need to do is set the default path for the latest Thym to be what's in
[3] and the latest version published there will be composited into a site that all
downstream users can enjoy.
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).