[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)]

    [ https://issues.jboss.org/browse/JBIDE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723043#comment-12723043 ] 

Nick Boldt edited comment on JBIDE-12662 at 10/1/12 5:34 PM:
-------------------------------------------------------------

promote.sh now pushes composite*.xml files into the parent folder for the component, eg.,

http://download.jboss.org/jbosstools/updates/integration/juno/core/freemarker/
http://download.jboss.org/jbosstools/updates/integration/juno/core/base/
http://download.jboss.org/jbosstools/updates/integration/juno/core/server/

Works great for SOA components too. Just needs to be run from this job (or similar) to produce the metadata.

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/

DO NOT have a solution yet for producing generic composite sites for grandparent folders, eg.,

http://download.jboss.org/jbosstools/updates/integration/juno/core/
or
http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/

as in theory those will be AGGREGATE sites, not composites.
                
      was (Author: nickboldt):
    promote.sh now pushes composite*.xml files into the parent folder for the component, eg.,

http://download.jboss.org/jbosstools/updates/integration/juno/core/freemarker/
http://download.jboss.org/jbosstools/updates/integration/juno/core/base/
http://download.jboss.org/jbosstools/updates/integration/juno/core/server/

Works great for SOA components too. Just needs to be run from this job (or similar) to produce the metadata.

DO NOT have a solution yet for producing generic composite sites for grandparent folders, eg.,

http://download.jboss.org/jbosstools/updates/integration/juno/core/
or
http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/

as in theory those will be AGGREGATE sites, not composites.
                  
> 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