[jbosstools-issues] [JBoss JIRA] (JBIDE-12662) generate composite metadata for soa components so we have a single URL for all child builds
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon Oct 1 17:35:03 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt closed JBIDE-12662.
------------------------------
Resolution: Done
Closing. I'm happy with the solution here and the docs are more or less up to date.
> generate composite metadata for soa components so we have a single URL for all child builds
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-12662
> URL: https://issues.jboss.org/browse/JBIDE-12662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, updatesite
> Affects Versions: 4.0.0.Alpha1, 4.0.0.Alpha1-SOA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.0.0.Beta1
>
>
> generate composite site metadata for all the contributed projects in a given folder so that end users can simply look to one URL instead of several -
> Per project, eg:
> * http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/modeshape/ composite*.xml
> * http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/modeshape/ composite*.xml
> * http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/switchyard/ composite*.xml
> and also
> * http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/ or
> * http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/
> Would need to be called by the promote.sh script so that it's always current w/ all the contributed content.
> Will also need this for JBT Core if components start releasing independent of the rest of the train (eg., finish ahead of schedule or need to respin a single component for maintenance w/o the rest of the train also respinning)
--
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
More information about the jbosstools-issues
mailing list