[
https://issues.jboss.org/browse/WELD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624283#comment-12624283
]
Ales Justin commented on WELD-952:
----------------------------------
Current workaround:
<!-- Redirect requests for the old repo to go to the new deprecated
repo -->
<mirror>
<id>deprecated-jboss-repo</id>
<name>Use new repo to handle requests to deprecated repo</name>
<mirrorOf>repository.jboss.org</mirrorOf>
<url>http://repository.jboss.org/nexus/content/repositories/deprecated</url>
</mirror>
<mirror>
<id>deprecated-jboss-repo2</id>
<name>Use new repo to handle requests to deprecated repo</name>
<mirrorOf>jboss</mirrorOf>
<url>http://repository.jboss.org/nexus/content/repositories/deprecated</url>
</mirror>
> Fix deprecated dependencies in jboss test harness
> -------------------------------------------------
>
> Key: WELD-952
> URL: https://issues.jboss.org/browse/WELD-952
> Project: Weld
> Issue Type: Enhancement
> Components: Testing Infrastructure (Mocks and Harness Integration)
> Reporter: Paul Gier
>
> The jboss test harness currently depends on the deprecated jboss repository
> (repository.jboss.org/maven2) and uses a lot of bad dependencies. This makes
> it impossible to build weld-core from outside the VPN. These dependencies
> should be cleaned up for a new release of the test harness, and weld-core
> should be updated to the new release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
