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

Nick Boldt commented on JBIDE-18869:
------------------------------------

I've created a Jenkins job to perform the mirroring from Eclipse to JBoss:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-requirements/

By default it'll push to http://download.jboss.org/jbosstools/builds/staging/jbosstools-requirements_thym/SNAPSHOT/

But if you want to cut over a specific milestone into /updates/requirements/, you can pass in some value of version, such as 0.1.0-SNAPSHOT-201412181815, and end up with:

http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAPSHOT-201412181815/

Then all we need to do is ensure that the JBT parent pom uses the correct mirror URL.

Note that when we start rolling out the path changes in JBDS-3208, this job will need to be tweaked to publish to the new paths too. (cc: [~mickael_istria] [~gercan] [~maxandersen])

{quote}And am I blind or is there not a PR for the parent pom that is missing to define the thym repo ?{quote}
Do you mean the first PR listed above? https://github.com/jbosstools/jbosstools-build/pull/161/files 

{quote}this is just for 4.3.0 not 4.2.0 ?{quote}
We could backport this to 8.1 if we wanted. Depends on how many more Thym builds will be needed in the 8.x stream, I guess.

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



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)