maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MSKINS-127) For all http://maven.apache.org/ pages it take 2 minutes to see content in China
Date Sun, 22 May 2016 18:48:12 GMT

    [ https://issues.apache.org/jira/browse/MSKINS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295677#comment-15295677
] 

Hervé Boutemy commented on MSKINS-127:
--------------------------------------

I don't see how to reasonably cheat: parent 30 site.xml should refer to fluido 1.6, and fluido
1.6 should have parent 30 as parent

And I don't see pressure also to upgrade parent to Fluido 1.6: the issue is there for years,
for many components (near 100). And for the few components that will be released after parent
30 is released without using Fluido 1.6 by default, setting it on components to prepare the
release is not a big issue
What I want is to have Maven main site fixed ASAP: it is already done, without waiting for
any release (pom or skin)

Then what is important for now is to confirm the issue is fixed on https://maven.apache.org/
and Google Analytics still works as previously

Fluido 1.6 release will come just after parent 30, and will be used by copy/pasting in each
component site.xml until parent 31 is released

> 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)

Mime
View raw message