On 24 April 2016 at 20:02, Kristian Rosenvold wrote:
> 22. apr. 2016 15.38 skrev "sebb" :
>
>> On 22 April 2016 at 12:29, Benson Margulies wrote:
>> > I thought I saw it. I guess I was wrong. I wonder what's taking so long?
>>
>> Even when Central is working well, it can take several hours (up to
22. apr. 2016 15.38 skrev "sebb" :
> On 22 April 2016 at 12:29, Benson Margulies wrote:
> > I thought I saw it. I guess I was wrong. I wonder what's taking so long?
>
> Even when Central is working well, it can take several hours (up to a
> day) to synch.
>
> That is partly why the instructions s
On 22 April 2016 at 12:29, Benson Margulies wrote:
> I thought I saw it. I guess I was wrong. I wonder what's taking so long?
Even when Central is working well, it can take several hours (up to a
day) to synch.
That is partly why the instructions say to wait.
> On Fri, Apr 22, 2016 at 1:46 AM,
https://issues.sonatype.org/browse/MVNCENTRAL-1060
On Fri, Apr 22, 2016 at 7:36 AM, Kristian Rosenvold
wrote:
> Looks like something is amiss with the central sync, the artifacts are at
> https://repository.apache.org/content/groups/public/commons-io/commons-io/
>
> You probably need to file an i
Looks like something is amiss with the central sync, the artifacts are at
https://repository.apache.org/content/groups/public/commons-io/commons-io/
You probably need to file an issue with mvncentral.
While you're at that, you can request in the same issue that all of the
"commons" artifacts be s
I thought I saw it. I guess I was wrong. I wonder what's taking so long?
On Fri, Apr 22, 2016 at 1:46 AM, Gary Gregory wrote:
> It's not on Central yet for example:
> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22commons-io%22%20AND%20a%3A%22commons-io%22
>
> G
>
> On Thu, Apr 21, 2016 at 6:
It's not on Central yet for example:
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22commons-io%22%20AND%20a%3A%22commons-io%22
G
On Thu, Apr 21, 2016 at 6:38 PM, Benson Margulies
wrote:
> On Thu, Apr 21, 2016 at 9:34 PM, sebb wrote:
> > The announce message should not be sent until a day o
On Thu, Apr 21, 2016 at 9:34 PM, sebb wrote:
> The announce message should not be sent until a day or so after the
> artifacts have been published in order to give time for the mirrors to
> catch up.
>
> At that point the site can be updated, the announce sent, and older
> versions removed.
>
> Ot
The announce message should not be sent until a day or so after the
artifacts have been published in order to give time for the mirrors to
catch up.
At that point the site can be updated, the announce sent, and older
versions removed.
Otherwise some users will get 404s
This should be explained i
