[
https://issues.apache.org/jira/browse/MSKINS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295662#comment-15295662
]
Michael Osipov commented on MSKINS-127:
---------------------------------------
You are right. It is a chicken-and-egg-problem. You can trick the system and
publish both at the same time. Having them locally will probably work. I think,
it work out for Central too.
> For all http://maven.apache.org/ pages it take 2 minutes to see content in
> China
> --------------------------------------------------------------------------------
>
> Key: MSKINS-127
> URL: https://issues.apache.org/jira/browse/MSKINS-127
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
> Affects Versions: fluido-1.5
> Environment: a device behind Great Firewall or google.com not
> available
> Reporter: Paul Verest
>
> For all http://maven.apache.org/ pages it take 2 minutes to see content,
> because page rendeing depends on getting to files
> - https://www.google.com/coop/cse/brand
> - https://apis.google.com/js/plusone.js
> see
> http://stackoverflow.com/questions/36959899/maven-site-google-issue-in-china
> As far as I know, it is generally good practice to put all script in the end
> of body, so that page is visible even if any 3rd party server fail the moment
> the page is requests.
> This is major bug as it affects many users, the reason it was not filed
> before is English skill, motivation and where to raise.
> Please review all page for 3rd party loads to insure that generated site will
> work even on PC without Internet access.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
