Hi, Ah, arrow-flight-*.pom exists on our CI artifacts: https://github.com/ursacomputing/crossbow/releases/tag/nightly-2022-02-17-0-github-java-jars
I don't know why our upload script https://github.com/apache/arrow/blob/master/dev/release/06-java-upload.sh doesn't upload it... Could you take a look at it? Thanks, -- kou In <cabr4zata2bwatbhoic_enfwemzpynvhyys895+5rjxpcgur...@mail.gmail.com> "Re: Is 7.0.0 release missing the Java arrow-flight POM?" on Thu, 17 Feb 2022 14:14:52 -0800, Bryan Cutler <cutl...@gmail.com> wrote: > Yes, it's a little confusing. The original arrow-flight was when the Flight > implementation was a single module, then it got split into flight-core and > flight-grpc and arrow-flight was no more Now it's back but only as a parent > POM. I think the current structure seems correct, so I'm not sure if we > would want to go back to using flight-core as the parent. Is it possible to > deploy just the arrow-flight POM? Otherwise, people can't use Flight for > this release without some kind of hack. > > On Thu, Feb 17, 2022 at 12:45 PM Sutou Kouhei <k...@clear-code.com> wrote: > >> Hi, >> >> It seems that arrow-flight isn't released after 0.15.1: >> https://repo1.maven.org/maven2/org/apache/arrow/arrow-flight/ >> >> But flight-core is released since 0.16.0: >> https://repo1.maven.org/maven2/org/apache/arrow/flight-core/ >> >> flight-grpc is also released: >> https://repo1.maven.org/maven2/org/apache/arrow/flight-grpc/ >> >> Can we use flight-core (and flight-grpc) instead of >> arrow-flight? >> >> Thanks, >> -- >> kou >> >> In <cabr4zarittgsrtd3oyjamapkemnc2jeur0h-ygznscswl-t...@mail.gmail.com> >> "Is 7.0.0 release missing the Java arrow-flight POM?" on Thu, 17 Feb >> 2022 09:48:57 -0800, >> Bryan Cutler <cutl...@gmail.com> wrote: >> >> > Hi All, >> > >> > Congrats on the 7.0.0 release! I was trying it out and got an error not >> > being able to find arrow-flight-7.0.0.pom. This looks like a new parent >> POM >> > for Flight, so I checked maven central and don't see it deployed there. >> Not >> > sure what could have happened, but maybe it's only me. Anyone else seeing >> > the same issue? >> > >> > Thanks, >> > Bryan >>