You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dan Tran <da...@gmail.com> on 2016/12/11 18:59:52 UTC
[HEADS UP] Releasing maven-wagon-2.11
Hi
I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time.
Let me know if you need me to wait
Thanks
-Dan
Re: [HEADS UP] Releasing maven-wagon-2.11
Posted by Michael Osipov <mi...@apache.org>.
Am 2016-12-23 um 07:26 schrieb Dan Tran:
> I am seeing this at my local build
>
> testConnectNullRepository(org.apache.maven.wagon.AbstractWagonTest)
> Time elapsed: 0.017 sec <<< ERROR!
> java.lang.NullPointerException: repository cannot be null
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:181)
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:134)
> at org.apache.maven.wagon.AbstractWagonTest.testConnectNullRepository(AbstractWagonTest.java:514)
>
>
>
> must have something to do with
>
> 1. [WAGON-473] Don't abuse IllegalArgumentException to intercept null
> input — michaelo <http://10.0.0.9:8080/user/michaelo/> / detail
> <http://10.0.0.9:8080/view/wagon/job/wagon/job/maven-wagon/63/changes#30631655e8f6cdf121161b3ca09e3da0134a5198>
I will have a look. Really weird, I ran all ITs several times. Thanks
for testing!
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] Releasing maven-wagon-2.11
Posted by Michael Osipov <mi...@apache.org>.
Am 2016-12-23 um 07:26 schrieb Dan Tran:
> I am seeing this at my local build
>
> testConnectNullRepository(org.apache.maven.wagon.AbstractWagonTest)
> Time elapsed: 0.017 sec <<< ERROR!
> java.lang.NullPointerException: repository cannot be null
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:181)
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:134)
> at org.apache.maven.wagon.AbstractWagonTest.testConnectNullRepository(AbstractWagonTest.java:514)
>
>
>
> must have something to do with
>
> 1. [WAGON-473] Don't abuse IllegalArgumentException to intercept null
> input — michaelo <http://10.0.0.9:8080/user/michaelo/> / detail
> <http://10.0.0.9:8080/view/wagon/job/wagon/job/maven-wagon/63/changes#30631655e8f6cdf121161b3ca09e3da0134a5198>
Issue is fixed. Seems like that was on oversight, I haven't noticed the
Jenkins failures for some reasons.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] Releasing maven-wagon-2.11
Posted by Dan Tran <da...@gmail.com>.
I am seeing this at my local build
testConnectNullRepository(org.apache.maven.wagon.AbstractWagonTest)
Time elapsed: 0.017 sec <<< ERROR!
java.lang.NullPointerException: repository cannot be null
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:181)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:134)
at org.apache.maven.wagon.AbstractWagonTest.testConnectNullRepository(AbstractWagonTest.java:514)
must have something to do with
1. [WAGON-473] Don't abuse IllegalArgumentException to intercept null
input — michaelo <http://10.0.0.9:8080/user/michaelo/> / detail
<http://10.0.0.9:8080/view/wagon/job/wagon/job/maven-wagon/63/changes#30631655e8f6cdf121161b3ca09e3da0134a5198>
On Tue, Dec 20, 2016 at 12:38 PM, Michael Osipov <mi...@apache.org>
wrote:
> Am 2016-12-11 um 19:59 schrieb Dan Tran:
>
>> Hi
>>
>> I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time.
>> Let me know if you need me to wait
>>
>
> Dan,
>
> you can start with your preperations. I have done my changes.
>
>
> Michael
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [HEADS UP] Releasing maven-wagon-2.11
Posted by Michael Osipov <mi...@apache.org>.
Am 2016-12-11 um 19:59 schrieb Dan Tran:
> Hi
>
> I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time.
> Let me know if you need me to wait
Dan,
you can start with your preperations. I have done my changes.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] Releasing maven-wagon-2.11
Posted by Dan Tran <da...@gmail.com>.
Sure
-Dan
On Mon, Dec 12, 2016 at 1:06 PM, Michael Osipov <mi...@apache.org> wrote:
> Am 2016-12-11 um 19:59 schrieb Dan Tran:
>
>> Hi
>>
>> I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time.
>> Let me know if you need me to wait
>>
>
> Can you hold it for a week? I am currently investigating an issue with
> duplicate dependencies for the HTTP provider. At the end, several artifacts
> land in {maven.home}/lib twice.
>
> This is worth fixing in 2.11 for Maven 3.4.
>
> Thanks,
>
> Michael
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [HEADS UP] Releasing maven-wagon-2.11
Posted by Michael Osipov <mi...@apache.org>.
Am 2016-12-11 um 19:59 schrieb Dan Tran:
> Hi
>
> I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time.
> Let me know if you need me to wait
Can you hold it for a week? I am currently investigating an issue with
duplicate dependencies for the HTTP provider. At the end, several
artifacts land in {maven.home}/lib twice.
This is worth fixing in 2.11 for Maven 3.4.
Thanks,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org