[
http://jira.codehaus.org/browse/MANTTASKS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227866#action_227866
]
Knut Forkalsrud commented on MANTTASKS-191:
-------------------------------------------
I have the same experience. Even if I name my repository "central" it will not
override the builtin "central", but instead append to it.
Here's my sample ant task (using maven-ant-tasks 2.1.0)
<target name="init">
<artifact:dependencies pathId="dependency.classpath"
filesetId="dependency.fileset">
<remoteRepository id="central"
url="http://mycompany.net/nexus/content/repo"/>
<dependency groupId="foo" artifactId="bar" version="3.8.2"/>
</artifact:dependencies>
</target>
A few lines of output from "ant -v compile":
[artifact:dependencies] Using remote repositories:
- id=central, url=http://mycompany.net/nexus/content/repo, releases=enabled,
snapshots=enabled
- id=central, url=http://repo1.maven.org/maven2, releases=enabled,
snapshots=disabled
org.apache.maven:super-pom:jar:2.0 (selected)
> No explanation of how to use multiple Maven repositories to resolve
> dependencies
> --------------------------------------------------------------------------------
>
> Key: MANTTASKS-191
> URL: http://jira.codehaus.org/browse/MANTTASKS-191
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.1.0
> Reporter: SebbASF
>
> There does not seem to be any documentation on how to use multiple
> repositories when resolving dependencies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
