Hi Jason, I think Piotr's failure was an attempt to download a dependency of a Maven plugin which should come from Maven Central. Om's errors were from uploading to repository.a.o and not Maven Central.
I found this article about proxies and Maven: https://stackoverflow.com/questions/38329243/maven-dependencies-are-not-getting-downloaded-proxy-issues?rq=1 I don’t know if Piotr is running behind a proxy or not, though. Thanks, -Alex On 10/12/18, 2:34 PM, "Guild, Jason A (DOT)" <jason.gu...@alaska.gov> wrote: Forgive my asking perhaps silly questions. Why in the world does the Royale release script have a dependency on publishing directly to Maven Central? Doesn't Apache maintain its own Maven repository of apache-produced artifacts? Isn't that what repo.maven.apache.org is? Why can't Royale publish to that? The artifacts successfully published there could be mirrored to other public repositories after the release is complete. Jason On 10/12/2018 12:01 PM, Piotr Zarzycki wrote: > Unfortunately I got the same result as OM:( Something is really wrong with > Maven central, cause I can't believe that we all have bad internet > connection.:)
