[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=12776944#comment-12776944 ] 

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

My understanding is that this "TP" repo contains the "extra" dependencies required by JBDS-IS components and would be used by JBDS-IS to resolve those dependencies.

As far as JBT-IS goes, it is my understanding that these referenced repositories are added as references to the JBT-IS aggregate repository (as the "TP" repository is not used by JBT-IS) and thus this issue only applies to JBDS-IS.

Specific answers:
1. yes
2. yes, however the "TP" repo is not used by JBT-IS, at least as far as I know.
3. I thought that's what the purpose of this "TP" repo was.
4. Not sure I understand the question, but no.  JBT references jboss.org and JBDS references jboss.com.  The JBT-IS dependencies are resolved using repo references in the aggregate repo (at least they used to be).

                
> 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