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

[Rob Cernich (JIRA)]

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

Rob Cernich commented on JBTIS-89:
----------------------------------

Hey Nick, I think that's what I'm talking about.  I'm talking about the p2 repository created using the mirror tp mojo.  That repo has all the "extra" dependencies required by IS, above and beyond the core platform.  The problem is, that repo contains references to repositories on jboss.org.

Here's how I discovered this.  I upgraded SwitchYard to use updated dependencies of Graphiti and EMF compare.  I then took an instance of JBDS, added update sites pointing to my local SwitchYard site and the p2 TP mirror created by integration-stack/target-platform.  After installing SwitchYard, I had two additional update sites in JBDS pointing to jboss.org.  I removed the repository references from the p2 TP mirror's content.xml, tried the install again, and all was good.

Hope that helps explain the situation better.

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