Le samedi 11 octobre 2008, will vuong a écrit : > i think it is a bug actually. > > i declare the remote repo in my pom.xml. then i go into my local repo > cache and delete commons-logging, and then execute mvn dependency:list. > maven goes to the proper repo. > > i deleted commons-logging again in my local repo again and then i run my > ant build with the pom ref, and it goes to central to pull down > commons-logging instead of the repo declared in my pom. i add the remote > repo to the maven ant task, and then it pulls from the correct repo. ok, your concern is the precedence of multiple repositories containing an artifact: this is the first time someone reports this usage, then it is not really tested :)
> > i'm going to try to write up a test case this weekend. please open a Jira with this test case and I'll investigate regards, Hervé > > Hervé BOUTEMY wrote: > > Le vendredi 10 octobre 2008, will vuong a écrit : > >> if i have a pom.xml that i refer to in my ant build.xml and that pom.xml > >> declares a remote repo, does the maven ant task use the pom's remote > >> repo? > >> or do i also have to declare the remote repo inside the build.xml? > >> thanks > >> for the clarification. > > > > no, you don't need to declare the repo in your build.xml since it is in > > the > > pom.xml. > > A general rule is that Maven Ant Tasks do like Maven: if it is different, > > it > > is likely a bug and should be filed in JIRA. > > > > Regards, > > > > Hervé > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
