[jbosstools-issues] [JBoss JIRA] (JBTIS-89) target platform repo should not contain repository references

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBTIS-89:
---------------------------------

Here's what appears at the end of the content.xml file inside the content.jar file for the JBT-IS 4.1 site:

{code:title=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.0/content.jar}
  <references size="10">
      <repository options="1" type="0"
                  uri="http://download.jboss.org/jbosstools/updates/development/kepler/"
                  url="http://download.jboss.org/jbosstools/updates/development/kepler/"/>
      <repository options="1" type="1"
                  uri="http://download.jboss.org/jbosstools/updates/development/kepler/"
                  url="http://download.jboss.org/jbosstools/updates/development/kepler/"/>
      <repository options="1" type="0"
                  uri="http://download.jboss.org/jbosstools/updates/requirements/kepler/20130510-0900-M7/"
                  url="http://download.jboss.org/jbosstools/updates/requirements/kepler/20130510-0900-M7/"/>
      <repository options="1" type="1"
                  uri="http://download.jboss.org/jbosstools/updates/requirements/kepler/20130510-0900-M7/"
                  url="http://download.jboss.org/jbosstools/updates/requirements/kepler/20130510-0900-M7/"/>
      <repository options="1" type="0"
                  uri="http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/201305101845/"
                  url="http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/201305101845/"/>
      <repository options="1" type="1"
                  uri="http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/201305101845/"
                  url="http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/201305101845/"/>
      <repository options="1" type="0"
                  uri="http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.3.v20130509-1351-CI/"
                  url="http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.3.v20130509-1351-CI/"/>
      <repository options="1" type="1"
                  uri="http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.3.v20130509-1351-CI/"
                  url="http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.3.v20130509-1351-CI/"/>
      <repository options="1" type="0"
                  uri="http://download.jboss.org/jbosstools/updates/integration/kepler/core/locus/0.0.1.v20130507-2028-B7/"
                  url="http://download.jboss.org/jbosstools/updates/integration/kepler/core/locus/0.0.1.v20130507-2028-B7/"/>
      <repository options="1" type="1"
                  uri="http://download.jboss.org/jbosstools/updates/integration/kepler/core/locus/0.0.1.v20130507-2028-B7/"
                  url="http://download.jboss.org/jbosstools/updates/integration/kepler/core/locus/0.0.1.v20130507-2028-B7/"/>
   </references>
</repository>
{code}
                
> target platform repo should not contain repository references
> -------------------------------------------------------------
>
>                 Key: JBTIS-89
>                 URL: https://issues.jboss.org/browse/JBTIS-89
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Rob Cernich
>            Assignee: Paul Leacu
>            Priority: Critical
>
> I don't see how this repo could be used in a jbds setting when it contains repository references to jbt repositories.  My understanding was that this repo only contained the extra dependencies for jbt-is.  By including these references, if this repo is used in jbds, all those linked repos will be available too, polluting the pool of available features/bundles.

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