Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Kristian Rosenvold
Great stuff. I looked around a bit and there does not seem to be a workaround (like a System property that can be set)... Kristian 2013/8/31, Robert Scholte : > Nice :D > > Case closed > > Op Sat, 31 Aug 2013 23:39:31 +0200 schreef Hervé BOUTEMY > : > >> yeah, I just tested m-doap-p ITs with *MN

Re: What is the correct Git SCM URL for a branch?

2013-08-31 Thread Chris Graham
I did something similar in the Jazz provider. It's a complex URL, or can be if it needs to be, but it's still a single line. It's just a matter of making the parser smarted. And that's local to the provider, so go nuts. I also put lots of unit tests in there to illustrate the correct and incorrect

Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Robert Scholte
Nice :D Case closed Op Sat, 31 Aug 2013 23:39:31 +0200 schreef Hervé BOUTEMY : yeah, I just tested m-doap-p ITs with *MNG-5509 fix and it works!* *well done* *Regards,* *Hervé* Le samedi 31 août 2013 17:10:53 Hervé BOUTEMY a écrit : nice unit test now hack AbstractHttpClientWagon.setH

Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Hervé BOUTEMY
yeah, I just tested m-doap-p ITs with *MNG-5509 fix and it works!* *well done* *Regards,* *Hervé* Le samedi 31 août 2013 17:10:53 Hervé BOUTEMY a écrit : > nice unit test > > now hack AbstractHttpClientWagon.setHeaders to add a User-Agent header: > method.addHeader( "User-Agent", "

Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Hervé BOUTEMY
nice unit test now hack AbstractHttpClientWagon.setHeaders to add a User-Agent header: method.addHeader( "User-Agent", "test" ); and it works: - >> "GET /maven2/junit/junit/maven-metadata.xml HTTP/1.1[\r][\n]" - >> "Cache-control: no-cache[\r][\n]" - >> "Cache-store: no-store[\r][\n]

Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Robert Scholte
I'm not sure if this testcase does exactly the same thing, but the results are the same: failure due to an Access Denied error. --- package org.apache.maven.wagon.providers.http; import org.apache.maven.wagon.InputData; import org.apache.maven.wagon.repository.Repository; import org.apache.ma

Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Hervé BOUTEMY
it was merged with wagon-http-shared when working on WAGON-388 Regards, Hervé Le samedi 31 août 2013 14:51:31 Robert Scholte a écrit : > Where are the sources of wagon-http-shared4? > > I don't see them here: > > https://git-wip-us.apache.org/repos/asf/maven-wagon.git/?p=maven-wagon.git;a > =t

Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Robert Scholte
Where are the sources of wagon-http-shared4? I don't see them here: https://git-wip-us.apache.org/repos/asf/maven-wagon.git/?p=maven-wagon.git;a=tree;f=wagon-providers;h=1b6502eff9db183e9a72b44efff7fe5e0cb8da23;hb=HEAD Robert Op Sat, 31 Aug 2013 13:29:37 +0200 schreef Robert Scholte : Rec

Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Robert Scholte
Recently I noticed several threads at Stackoverflow mentioning the same exception. I've tried it with the following version (in this order): M3.1.0 > failed M3.0.4 > success M3.0.5 > success M3.1.0 > success So I changed the updatePolicy of the central repository to 'always'. Now it still succ

Re: IT failure on Maven-doap plugin with maven >3.0.3

2013-08-31 Thread Hervé BOUTEMY
Really strange I can reproduce m-doap-p IT failures from my machine but not m-eclipse-p ones notice in m-doap-p IT, the url should get a 404 not found but in m-eclipse-p IT, the url points to existing content IMHO, the behaviour change between Maven versions is tied to MNG-5175 change from wagon