[jbosstools-issues] [JBoss JIRA] (JBDS-2673) Can't build JBDS because of p2.mirrors

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBDS-2673:
--------------------------------------

This seems to be the culprit: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L28
Why is this line set? Is this necessary? It seems to override the effect of the unified.target profile.
                
> Can't build JBDS because of p2.mirrors
> --------------------------------------
>
>                 Key: JBDS-2673
>                 URL: https://issues.jboss.org/browse/JBDS-2673
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: updatesite
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>
> Tried to build JBDS 7.0.0.CR1 tonight in Jenkins, but got this instead:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/devstudio.product_70/347/console}
> [ERROR] Internal error: java.lang.RuntimeException: "Messages while reading artifacts from child repositories": ["Problems while reading artifacts from http://download.jboss.org/jbosstools/updates/requirements/kepler/201306260900-R": ["Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.eclipse.datatools.enablement.sqlite_1.0.0.v201002041100.jar.pack.gz"], "Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.eclipse.wst.internet.monitor.ui_1.0.608.v20130501_1206.jar.pack.gz"]]] -> [Help 1]
> {code}
> I thought we were filtering out all the external references from the metadata after we mirrored?

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