I get the same issue out of:

mvn -version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\apache-maven\bin\..
Java version: 11.0.6, vendor: Amazon.com Inc., runtime: C:\Program
Files\Amazon Corretto\jdk11.0.6_10
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

[ERROR] Errors:
[ERROR]   OsgiITest.loadBundle » IO Error resolving artifact
org.ops4j.pax.exam:pax-exam...
[INFO]
[ERROR] Tests run: 1170, Failures: 0, Errors: 1, Skipped: 9

Still guessing that it's a compatibility issue between a change in maven
central and pax-4.13.1

-Rob


On Mon, Feb 3, 2020 at 11:40 AM Rob Tompkins <chtom...@gmail.com> wrote:

>
>
> > On Feb 3, 2020, at 11:39 AM, Gary Gregory <garydgreg...@gmail.com>
> wrote:
> >
> > Just to be on the safe side I would update Java 8 and 11 to their
> > respective current versions. It probably won't help but you and I will at
> > least be on the same foundation aside from the OS.
>
> Agree. Good point there.
>
> >
> > Gary
> >
> > On Mon, Feb 3, 2020 at 11:21 AM Rob Tompkins <chtom...@gmail.com> wrote:
> >
> >> For what it’s worth, I get the failure regardless of whether or not I
> run
> >> the test with maven. The failure is in:
> >>
> >>
> >>
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:626)
> >>
> >> Which isn’t dependent upon maven at all actually. So, I suspect that
> maven
> >> has accommodated for the https, yet pax has not.
> >>
> >> If you declare your .m2 directory to be somewhere else, do you see the
> >> same failure?
> >>
> >> Also for what it’s worth, I’m running:
> >>
> >> chtompki@Robs-MacBook-Pro commons-compress-1.20-src % mvn -version
> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> >> Maven home: /usr/local/Cellar/maven/3.6.3/libexec
> >> Java version: 1.8.0_222, vendor: Amazon.com Inc., runtime:
> >>
> /Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/jre
> >> Default locale: en_US, platform encoding: UTF-8
> >> OS name: "mac os x", version: "10.15.2", arch: "x86_64", family: "mac"
> >> chtompki@Robs-MacBook-Pro commons-compress-1.20-src % java11
> >> chtompki@Robs-MacBook-Pro commons-compress-1.20-src % mvn -version
> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> >> Maven home: /usr/local/Cellar/maven/3.6.3/libexec
> >> Java version: 11.0.5, vendor: Amazon.com Inc., runtime:
> >> /Library/Java/JavaVirtualMachines/amazon-corretto-11.jdk/Contents/Home
> >> Default locale: en_US, platform encoding: UTF-8
> >> OS name: "mac os x", version: "10.15.2", arch: "x86_64", family: "mac"
> >>
> >>> On Feb 3, 2020, at 11:09 AM, Rob Tompkins <chtom...@gmail.com> wrote:
> >>>
> >>> Right….I get the artifact from maven central over https…let me make
> sure
> >> I’m on the latest maven version. -Rob
> >>>
> >>>> On Feb 3, 2020, at 11:08 AM, Stefan Bodewig <bode...@apache.org>
> wrote:
> >>>>
> >>>> On 2020-02-03, Rob Tompkins wrote:
> >>>>
> >>>>> I’m not sure what changed between yesterday and today, but it seems
> >> that the org.apache.commons.compress.OsgiTest is failing due to a 501
> being
> >> returned from
> >>
> http://repo1.maven.org/maven2/org/ops4j/pax/exam/pax-exam-inject/4.13.1/pax-exam-inject-4.13.1.jar
> >> <
> >>
> http://repo1.maven.org/maven2/org/ops4j/pax/exam/pax-exam-inject/4.13.1/pax-exam-inject-4.13.1.jar
> >>>
> >>>>
> >>>> That should be https rather than http. Maven Central requires TLS by
> >>>> now.
> >>>>
> >>>> I don't think Compress configures repositories explicitly, so it might
> >>>> be the version f Maven?
> >>>>
> >>>> Stefan
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >>>> For additional commands, e-mail: dev-h...@commons.apache.org
> >>>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
>
>

Reply via email to