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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBTIS-89:
-------------------------------------

[~pleacu] [~rcernich]: the remove.references.xml script is a way to get rid of dependencies.
The generate-repository-facade mojo also removes default references and is easier to integrate with Maven, and allows you to add some other references see https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/pom.xml#L32 and https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java#L346 ).

However, I don't understand why you get so many references on your site. It's probably caused by features defining reference to other sites, which is something deprecated as it does not provide enough control on final packaging.
                
> 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