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

[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15606: ------------------------------------ [~maxandersen], please read the README: https://github.com/jbosstools/jbosstools-build-sites/tree/jbosstools-4.1.... Then, look at the usage example here: https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.1.... Then, look at the job configuration here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-component... Due to a limitation in the way Maven works, the job is actually more efficient than the offline pom.xml by itself as it can wget the correct category.xml file BEFORE starting the maven job, rather than using the maven job to fetch the file. So, this isn't a very clean solution for offline use (you have to run the maven build twice locally, or once in Jenkins), but for the temporary fix we need to collect the individual component sites, it's sufficient. After we release 4.1.1, *we should release ALL the component sites* - I agree with you that that's better, though it's potentially more work than is needed. By doing so, we can cherry-pick which released components to include in the composite site (and therefore the aggregate site), vs. including new CI builds for components that have changed or will change for the JBT 4.2.0 release. (We already do this in part for JBT 4.1.1 for XulRunner, GWT, and Freemarker - http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... - I'll be adding BIRT, Hibernate Tools, and Portlet soon.) -- 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