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

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

Since we are just talking about using these nexus published sites for non-aggregated-releases nexus uptime is more than sufficient. If nexus is down - we can't build the projects anyway.

I don't understand why you would like to have a mix of some sites being published and others aggregated directly into the site. Uniformity seems better and unless i'm missing something simpler and faster to do and maintain.

About what is pushed I honestly don't see how https://github.com/jbosstools/jbosstools-build-sites/pull/108/files is supposed to work. It just declares an empty directory and a pom that moves/copies a category.xml.

i.e. where is the "tool" that is referenced in this jira that actually does the "job" 
                
> 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