Before I contact Maven mailing list I would like to try again release to see what I got.
On Sat, Oct 13, 2018, 11:28 AM Carlos Rovira <carlosrov...@apache.org> wrote: > Hi, commit done and seems no other side effect was done. So I think the > tweaks worked. > > El sáb., 13 oct. 2018 a las 11:18, Carlos Rovira (<carlosrov...@apache.org > >) > escribió: > > > Hi, > > > > about delete tag, I was investigating and did some tweaks to my system. > So > > we'll see in the next commit if it works. > > > > El sáb., 13 oct. 2018 a las 8:59, Carlos Rovira (< > carlosrov...@apache.org>) > > escribió: > > > >> Hi, > >> > >> I think asking ni maven list is our best bet since as we do here, surely > >> they can help and give some light on what's happening, so > >> +1 to ask in maven list > >> > >> > >> > >> El sáb., 13 oct. 2018 a las 7:56, Alex Harui (<aha...@adobe.com.invalid > >) > >> escribió: > >> > >>> No, some people think the script was trying to upload the RC to Maven > >>> Central instead of repository.apache.org. From my reading of the > logs, > >>> you had a problem downloading a Maven plugin from Maven Central which > is > >>> allowed, while Om was having trouble uploading to > repository.apache.org. > >>> > >>> I think we're ok as long as we can figure out why you and Om keep > >>> getting timeouts. There are plenty of articles about Maven and the > timeout > >>> but it all seems to be proxy related. If you are not using a proxy, > maybe > >>> there is an article out there that isn't about proxies. You could > also ask > >>> on a Maven mailing list to see if they've heard of this issue. > >>> > >>> -Alex > >>> > >>> On 10/12/18, 10:47 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> > >>> wrote: > >>> > >>> So the difference is that when we vote successful y for release we > >>> are > >>> uploading manually those artifacts? > >>> > >>> Automatic is not allowed? This is how I understand. > >>> > >>> Piotr > >>> > >>> On Sat, Oct 13, 2018, 7:40 AM Piotr Zarzycki < > >>> piotrzarzyck...@gmail.com> > >>> wrote: > >>> > >>> > Alex, > >>> > > >>> > I'm not running behind the proxy. > >>> > > >>> > Hi Dave, > >>> > > >>> > We are publishing only RC. Why it is against? > >>> > > >>> > Piotr > >>> > > >>> > On Sat, Oct 13, 2018, 1:05 AM Dave Fisher <dave2w...@comcast.net > > > >>> wrote: > >>> > > >>> >> > >>> >> > >>> >> Sent from my iPhone > >>> >> > >>> >> > On Oct 12, 2018, at 2:33 PM, Guild, Jason A (DOT) < > >>> >> jason.gu...@alaska.gov> wrote: > >>> >> > > >>> >> > Forgive my asking perhaps silly questions. > >>> >> > >>> >> +1 > >>> >> > >>> >> > > >>> >> > Why in the world does the Royale release script have a > >>> dependency on > >>> >> > publishing directly to Maven Central? > >>> >> > >>> >> That is likely against Apache Release Policy as well and must be > >>> changed. > >>> >> > >>> >> > > >>> >> > 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. > >>> >> > >>> >> Yes, exactly. > >>> >> > >>> >> Regards, > >>> >> Dave > >>> >> > >>> >> > 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.:) > >>> >> > > >>> >> > >>> >> > >>> > >>> > >>> > >> > >> -- > >> Carlos Rovira > >> http://about.me/carlosrovira > >> > >> > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > > > > > -- > Carlos Rovira > http://about.me/carlosrovira >
