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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-15606:
---------------------------------------------

For Kepler where this step was "missed" - why is it not enough to simply point to stable/kepler to get the freemarker 1.3.100 final versions ? You simply just put in the exact feature version.

And wouldn't it be better to actually build these sites and aggregate them than this "reverse option" ? 

or do you mean this is just for the kepler release and we do something better/more reliable for future releases ?
                
> 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