[
http://jira.codehaus.org/browse/MANTTASKS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184107#action_184107
]
Krashan Brahmanjara commented on MANTTASKS-157:
-----------------------------------------------
I can not agree with Benjamin.
In Maven 2.1 and 2.2 users can define mupltiple mirrors (for central too). This
feature is well documented on maven pages. It really works.
You can see searching method on console log :
artifact:dependencies] Downloading:
org/icefaces/icefaces/1.8.1/icefacs-1.8.1.pom from central
artifact:dependencies] Downloading:
org/icefaces/icefaces/1.8.1/icefacs-1.8.1.pom from apache.releases
artifact:dependencies] Downloading:
org/icefaces/icefaces/1.8.1/icefacs-1.8.1.pom from jboss.mirror
artifact:dependencies] Downloading:
org/icefaces/icefaces/1.8.1/icefacs-1.8.1.pom from krokodylowy3.thirdparty
artifact:dependencies] Downloading:
org/icefaces/icefaces/1.8.1/icefacs-1.8.1.pom from central
I suppose that maven-ant-tasks don't use maven install files so maven
configuration is useless and all should be defined in pom or ant file
> Manven-ant-tasks do not use servers list from maven conf
> --------------------------------------------------------
>
> Key: MANTTASKS-157
> URL: http://jira.codehaus.org/browse/MANTTASKS-157
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Affects Versions: 2.0.10
> Reporter: Krashan Brahmanjara
>
> I got simply ant and pom project. Settings file for maven 2.1 contains list
> of mirror servers.
> If I compile project by mvn package everything works ok - artifacts are
> downloaded
> if I compile the same project by ant and maven-ant-tasks some artifacts are
> not downloaded. it looks like the mirrors list are sometimes ignored.
> Current workaroud is add to pom.xml repository entries which are duplicate of
> mirrors from maven configuration.
> maven settings
> <mirrors>
> <mirror>
> <id>krokodylowy3</id>
> <url>http://krokodylowy3.webpark.pl/maven/m2/repository</url>
> <mirrorOf>central</mirrorOf>
> </mirror>
> <mirror>
> <id>Apache.releases</id>
> <url>https://repository.apache.org/content/repositories/releases/</url>
> <mirrorOf>central</mirrorOf>
> </mirror>
> <mirror>
> <id>Apache.snapshots</id>
> <url>https://repository.apache.org/content/repositories/snapshots/</url>
> <mirrorOf>central</mirrorOf>
> </mirror>
> <mirror>
> <id>repository.jboss.org</id>
> <url>http://repository.jboss.org/maven2</url>
> <mirrorOf>central</mirrorOf>
> </mirror>
> <mirror>
> <id>repo1.maven.org</id>
> <url>http://repo1.maven.org/maven2</url>
> <mirrorOf>*</mirrorOf>
> </mirror>
> </mirrors>
> workaround
> <repositories>
> <repository>
> <id>thirdparty</id>
> <name>krokodylowy3 thirdparty</name>
>
> <url>http://krokodylowy3.webpark.pl/maven/m2/repository</url>
> </repository>
> <repository>
> <id>jboss</id>
> <name>jboss thirdparty</name>
> <url>http://repository.jboss.org/maven2</url>
> </repository>
> </repositories>
--
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
