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

Nick Boldt edited comment on JBIDE-18869 at 12/19/14 12:09 PM:
---------------------------------------------------------------

Merged:
https://github.com/jbosstools/jbosstools-build/pull/161
https://github.com/jbosstools/jbosstools-build/pull/163

For review:
https://github.com/jbosstools/jbosstools-build-sites/pull/165
https://github.com/jbdevstudio/jbdevstudio-product/pull/253
https://github.com/jbosstools/jbosstools-target-platforms/pull/113

Also, would it make sense to have the parent pom's version of $\{eclipse-thym-site} point to the snapshots site [1] or a specific mirror we've already pulled?

And should we have to keep updating the parent pom  with each new version of Thym, or would it make sense to just set this in the aggregate site's pom [2] instead? 

[1] http://download.eclipse.org/thym/snapshots/
[2] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/pom.xml#L167

Or, I suppose we could have a Jenkins job that simply creates a mirror of the Thym stuff every time Gorkem decides it's time to pull new bits; then we could just have a generic URL like:

{code}
<eclipse-thym-site>${jbosstools-site-baseurl}/eclipse-thym_${jbosstools-site-stream}/${jbosstools-site-suffix}</eclipse-thym-site>
{code}

WDYT [~gercan] [~maxandersen] [~mickael_istria] ?


was (Author: nickboldt):
Merged:
https://github.com/jbosstools/jbosstools-build/pull/161
https://github.com/jbosstools/jbosstools-build/pull/163

For review:
https://github.com/jbosstools/jbosstools-build-sites/pull/165
https://github.com/jbdevstudio/jbdevstudio-product/pull/253
https://github.com/jbosstools/jbosstools-target-platforms/pull/113

Also, would it make sense to have the parent pom's version of $\{eclipse-thym-site} point to the snapshots site [1] or a specific mirror we've already pulled?

And should we have to keep updating the parent pom  with each new version of Thym, or would it make sense to just set this in the aggregate site's pom [2] instead? 

[1] http://download.eclipse.org/thym/snapshots/
[2] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/pom.xml#L167

Or, I suppose we could have a Jenkins job that simply creates a mirror of the Thym stuff every time Gorkem decides it's time to pull new bits; then we could just have a generic URL like:

{code}
<eclipse-thym-site>$\{jbosstools-site-baseurl}/eclipse-thym_$\{jbosstools-site-stream}/$\{jbosstools-site-suffix}</eclipse-thym-site>
{code}

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