[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:
------------------------------------
Some composite*.xml files are generated. Some are not. In this context, they WILL be
generated once JBIDE-15482 is complete, but for older releases and other implementations,
NO, they are NOT generated.
"#2 and #3 could be fixed - i'm still wondering why these even have to be
separate sites." << What do you mean? How?
"makes more sense to publish these intermediate sites instead of creating them from
an previously generated aggregate" << YES. But it would help to know in advance
which ones won't be changing, so I don't need to create mirrors of things that
WILL be changing (like the Base or Server component, because that's always being
updated/refactored/improved).
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