I don't know if plugins remain on Apache's maven repo after they are pushed to
Maven Central, but for me, I was having trouble pushing the artifacts to
Apache's maven repo if my network was too busy. No matter what, we have to get
the bits from the developer's machine to some server, and that communication
can fail. IIRC, that communication to the Apache maven repo was way more
likely to fail than downloads from Maven Central, but if we are going to make
Maven artifacts available, which I think we should, we pretty much have to
communicate with that server. Hopefully the next people to try it will try to
have less going on in their network, but also, we know that there is nothing
wrong with the "process" so problems like these can be investigated as a server
communication problem and not a problem with the scripts.
My 2 cents,
-Alex
On 11/15/18, 8:50 AM, "Guild, Jason A (DOT)" <jason.gu...@alaska.gov> wrote:
Any dependency on a public repository, even just for downloading, is
problematic from a consistency POV because the repo could be down/slow
or suddenly resolve to wrong/missing artifacts.
Maybe all plugins needed by the build could just be mirrored from
Apache's maven repository?
On 11/15/2018 1:02 AM, Alex Harui wrote:
> Only after we approve the release do the artifacts get pushed to Maven
Central. One of the RMs got an error DOWNLOADING a Maven plugin from Maven
Central. There is nothing wrong with doing that.
