+1 from me.
On Sun, Dec 29, 2013 at 9:36 PM, Benson Margulies wrote:
> Hi,
>
> We solved 3 issues:
>
>
> ** Improvement
> * [WAGON-401] - Access Denied due to missing User-Agent
> * [WAGON-402] - Upgrade Apache HttpClient based wagon provider to
> HttpClient 4.3
> * [WAGON-403] - SSH
Hi,
We solved 3 issues:
** Improvement
* [WAGON-401] - Access Denied due to missing User-Agent
* [WAGON-402] - Upgrade Apache HttpClient based wagon provider to
HttpClient 4.3
* [WAGON-403] - SSH agent support for wagon-ssh
There are still a couple of issues left in JIRA:
http://ji
> From: mgai...@hotmail.com
> To: dev@maven.apache.org
> Subject: RE: Plugin phase awareness...
> Date: Sun, 29 Dec 2013 17:46:29 -0500
>
>
>
>
>
>
> > Date: Sun, 29 Dec 2013 15:13:12 +
> > Subject: Re: Plugin phase awareness...
> > From: stephen.alan.conno...@gmail.com
> > To: dev@
I ran one build of maven-wagon as a warmup for releasing. No problems.
All subsequent attempts have died in the http wagon tests, with a
variety of failures.
Has anyone got some reliable way to run these builds?
-
To unsubscribe
This actually provides another way to know how the Mojo was invoked.
Not bad.
:)
2013/12/29 Stephen Connolly
> Are you running the mojo directly in your testing by any chance?
>
> Eg
>
> mvn short-name:goal
>
> As opposed to
>
> mvn phase
>
> Because if the former, then the phase is null as th
> Date: Sun, 29 Dec 2013 15:13:12 +
> Subject: Re: Plugin phase awareness...
> From: stephen.alan.conno...@gmail.com
> To: dev@maven.apache.org
>
> Are you running the mojo directly in your testing by any chance?
>
> Eg
>
> mvn short-name:goal
MG>Correct I was testing in this fashion
I did the last 2.5 one, that had two major problems: 2G file limit and
httpclient 4.x pool pollution problem
As I see, there are 3 issues solved
http://jira.codehaus.org/issues/?jql=project%20%3D%20WAGON%20AND%20fixVersion%20%3D%20%222.6%22%20AND%20status%20%3D%20Closed%20ORDER%20BY%20priority
Are you running the mojo directly in your testing by any chance?
Eg
mvn short-name:goal
As opposed to
mvn phase
Because if the former, then the phase is null as the execution was not
bound to a phase.
I have not used this specific property before, so cannot speak to whether
it works when boun
Morning All-
Even after downloading maven-core 3.1.1 source and re-compiling to new
maven-core-3.1.1.jar distro
and forcing maven-core-3.1.1 dependency into maven-surefire-plugin
I could not get ${mojoExecution.lifecyclePhase} to display anything other than
null
https://jira.codehaus.org
