[jbosstools-issues] [JBoss JIRA] (JBTIS-89) target platform repo should not contain repository references
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Sat May 25 13:08:06 EDT 2013
[ https://issues.jboss.org/browse/JBTIS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777011#comment-12777011 ]
Nick Boldt commented on JBTIS-89:
---------------------------------
Ah, my mistake. Not sure if you can mirror w/o including references, since that's the way p2 creates a mirror.
However, you can remove references immediately after mirroring, simply by removing the chunk of XML that contains the <references>.
Here's an ant script that you could call via antrun plugin from your pom, which uses XSLT to find and remove the entire <references> node in the content.xml:
https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/updates/requirements/remove.references.xml
> 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
More information about the jbosstools-issues
mailing list