[
https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15606:
------------------------------------
I mean we copy the bits included in
http://download.jboss.org/jbosstools/updates/stable/kepler/ to child sites like
http://download.jboss.org/jbosstools/updates/stable/kepler/core/freemarke...
so that future builds of JBT 4.1.x can be aggregated from the released Freemarker
1.3.100.Final bits.
Point of this is so that staging folders like
http://download.jboss.org/jbosstools/builds/staging/jbosstools-freemarker...
don't have to be kept indefinitely, and in the event we accidentally delete one, we
have a way to recreate a useful update site from the previously released binary bits w/o
having to rebuild from an old tag.
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