[jbosstools-issues] [JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809510#comment-12809510 ] 

Nick Boldt commented on JBIDE-15606:
------------------------------------

In the past this step's not been needed, because the whole stack just rebuilt itself even if nothing had changed.

But going forward, we're trying to be better about "nothing changed == no respins", so I need to have 1 repo per component that won't be changing in the next release.

The reason I don't want to put in specific versions is that it means maintaining that information in multiple places:

1. http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.kepler/ composite*.xml
2. https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.1.x/aggregate/site/category.xml
3. https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.1.x/aggregate/webtools-site/category.xml
etc.

What I'd like to do is find the midground between "release every component by itself AS WELL as JBT aggregate" (too much work - especially if some projects start out unchanged for Alpha1 and then later end up changing for Alpha2, like Forge; or like Freemarker which didn't change at all during the JBT 4.1.0 cycle until after Beta, IIRC) and "oops, we need to go back and re-aggregate a few projects". 


                
> build tool to regenerate component update sites from published JBT aggregate
> ----------------------------------------------------------------------------
>
>                 Key: JBIDE-15606
>                 URL: https://issues.jboss.org/browse/JBIDE-15606
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, updatesite
>    Affects Versions: 4.1.1.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.1.1.Beta1
>
>
> When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so.
> We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects.
> This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira