[jbosstools-issues] [JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBTIS-141 at 8/15/13 4:37 PM:
-----------------------------------------------------------

*JBTIS 4.1.x*: https://github.com/jbosstools/jbosstools-integration-stack/pull/71

*JBTIS 4.0.x*: https://github.com/jbosstools/jbosstools-integration-stack/pull/72

                
      was (Author: nickboldt):
    *JBTIS 4.1.x*

https://github.com/jbosstools/jbosstools-integration-stack/pull/71

*JBTIS 4.0.x*

https://github.com/jbosstools/jbosstools-integration-stack/pull/72

                  
> fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb
> -----------------------------------------------------------------------------
>
>                 Key: JBTIS-141
>                 URL: https://issues.jboss.org/browse/JBTIS-141
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: BPEL, distribution, ESB, jBPM3
>    Affects Versions: 4.0.0, 4.1.0.Final
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.0.1, 4.1.1
>
>
> Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams.
> Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too.

--
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