[
https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15606:
------------------------------------
PR pushed to master; similar PR pushed to 4.1.x branch so if we need to use this again we
can. I would prefer to not have to but it's nice to have a backup approach.
Using combination of new job + jbosstools-promote job, we now have published all the _410
CI builds to here:
http://download.jboss.org/jbosstools/updates/stable/kepler/core/
* birt 1.5.0,
* hibernate 3.7.0,
* portlet 1.5.0,
* project-examples 1.5.1 (JBT 4.1.0.1 patch site, includes only the changed feature not
the whole jbosstools-central site)
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