From issues-return-136477-archive-asf-public=cust-asf.ponee.io@maven.apache.org Sat Aug 18 19:56:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id AD4E3180657 for ; Sat, 18 Aug 2018 19:56:04 +0200 (CEST) Received: (qmail 21851 invoked by uid 500); 18 Aug 2018 17:56:03 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 21840 invoked by uid 99); 18 Aug 2018 17:56:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Aug 2018 17:56:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 695341804B8 for ; Sat, 18 Aug 2018 17:56:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id wV3Kxd4OhBwR for ; Sat, 18 Aug 2018 17:56:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7F2915F238 for ; Sat, 18 Aug 2018 17:56:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C29FCE0234 for ; Sat, 18 Aug 2018 17:56:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2DE6223F98 for ; Sat, 18 Aug 2018 17:56:00 +0000 (UTC) Date: Sat, 18 Aug 2018 17:56:00 +0000 (UTC) From: "Stephen Colebourne (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MSITE-639) sub-project tries to fetch a site_en.xml even though no locales are configured MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MSITE-639?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16584= 858#comment-16584858 ]=20 Stephen Colebourne edited comment on MSITE-639 at 8/18/18 5:55 PM: ------------------------------------------------------------------- I can't reopen this (as I don't have permission), but I believe it is still= a problem with the latest plugins. However it is transient - it does not h= appen every time. I haven't tried the projects above, but can point you at = Joda-Money for example. [https://github.com/JodaOrg/joda-money]=C2=A0as of = the 18th August. I suspect that it does not always fail the first time as the failure is due= to network issues of some kind, such as Maven Central being flaky. This is= particularly a problem if multiple repos are being queried. Without invest= igating further, my gut feeling is that the code only=C2=A0determines that = the file is missing if=C2=A0 _all_=C2=A0the remote repos=C2=A0say its not t= here. Thus if one repo is slow, or returns something other than 404 (eg. a = security access failure) I've seen the problem on Java 8, 9 and 10 builds on Travis. For example, I = pushed three separate Joda projects in the last hour which performed 9 buil= ds on Travis - with two Java 9 failures and one Java 10. ie. the same commi= t in the same Travis build failing on 10 but working on 9 and vice versa). = My next set of=C2=A09 builds saw 4 fail and 5 succeed. This is the section of the build in my case when it succeeds, as can be see= n it queries multiple repos: =C2=A0 {noformat} [INFO] Done SpotBugs Analysis.... [INFO] Rendering site with default locale= English (en) [INFO] Downloading from sonatype: https://oss.sonatype.org/co= ntent/repositories/releases/org/joda/joda-parent/1.3/joda-parent-1.3-site_e= n.xml [INFO] Downloading from sonatype-apache: https://repository.apache.or= g/releases/org/joda/joda-parent/1.3/joda-parent-1.3-site_en.xml [INFO] Down= loading from central: http://repo.maven.apache.org/maven2/org/joda/joda-par= ent/1.3/joda-parent-1.3-site.xml [INFO] Downloaded from central: http://rep= o.maven.apache.org/maven2/org/joda/joda-parent/1.3/joda-parent-1.3-site.xml= (87 B at 4.1 kB/s) [INFO] Relativizing decoration links with respect to lo= calized project URL: http://www.joda.org/joda-beans/{noformat} =C2=A0 Note that until these most recent builds, my parent project had no `site.x= ml`.=C2=A0The purpose of my change today was to publish site.xml using site= :attach-descriptor to avoid this problem. However, since=C2=A0it is still l= ooking for site_en.xml which is not published, I still get the error, which= is a pain. For the logs produced when it fails, see here: [https://travis-ci.org/JodaO= rg/joda-convert/jobs/417679434]=C2=A0As can be seen, the "connection timed = out", but the real question is why is it trying to query the _en file in th= e first place? PS. When both=C2=A0site_en.xml and=C2=A0site.xml are present, mvn site:atta= ch-descriptor only attaches=C2=A0the _en variant! was (Author: scolebourne@joda.org): I can't reopen this (as I don't have permission), but I believe it is still= a problem with the latest plugins. However it is transient - it does not h= appen every time. I haven't tried the projects above, but can point you at = Joda-Money for example. [https://github.com/JodaOrg/joda-money]=C2=A0as of = the 18th August. I suspect that it does not always fail the first time as the failure is due= to network issues of some kind, such as Maven Central being flaky. This is= particularly a problem if multiple repos are being queried. Without invest= igating further, my gut feeling is that the code only=C2=A0determines that = the file is missing if=C2=A0 _all_=C2=A0the remote repos=C2=A0say its not t= here. Thus if one repo is slow, or returns something other than 404 (eg. a = security access failure) I've seen the problem on Java 8, 9 and 10 builds on Travis. For example, I = pushed three separate Joda projects in the last hour which performed 9 buil= ds on Travis - with two Java 9 failures and one Java 10. ie. the same commi= t in the same Travis build failing on 10 but working on 9 and vice versa). = My next set of=C2=A09 builds saw 4 fail and 5 succeed. This is the section of the build in my case when it succeeds, as can be see= n it queries multiple repos: =C2=A0 {noformat} [INFO] Done SpotBugs Analysis.... [INFO] Rendering site with default locale= English (en) [INFO] Downloading from sonatype: https://oss.sonatype.org/co= ntent/repositories/releases/org/joda/joda-parent/1.3/joda-parent-1.3-site_e= n.xml [INFO] Downloading from sonatype-apache: https://repository.apache.or= g/releases/org/joda/joda-parent/1.3/joda-parent-1.3-site_en.xml [INFO] Down= loading from central: http://repo.maven.apache.org/maven2/org/joda/joda-par= ent/1.3/joda-parent-1.3-site.xml [INFO] Downloaded from central: http://rep= o.maven.apache.org/maven2/org/joda/joda-parent/1.3/joda-parent-1.3-site.xml= (87 B at 4.1 kB/s) [INFO] Relativizing decoration links with respect to lo= calized project URL: http://www.joda.org/joda-beans/{noformat} =C2=A0 Note that until these most recent builds, my parent project had no `site.xm= l`.=C2=A0The purpose of my change today was to publish site.xml using site:= attach-descriptor to avoid this problem. However, since=C2=A0it is still lo= oking for site_en.xml which is not published, I still get the error, which = is a pain. For the logs produced when it fails, see here: [https://travis-ci.org/JodaO= rg/joda-convert/jobs/417679434]=C2=A0As can be seen, the "connection timed = out", but the real question is why is it trying to query the _en file in th= e first place? =C2=A0 > sub-project tries to fetch a site_en.xml even though no locales are confi= gured > -------------------------------------------------------------------------= ----- > > Key: MSITE-639 > URL: https://issues.apache.org/jira/browse/MSITE-639 > Project: Maven Site Plugin > Issue Type: Bug > Affects Versions: 3.0 > Environment: Windows 7 64bit, Sun JDK 1.6.0_27 > Reporter: Martin Goldhahn > Priority: Major > Attachments: parent-project.zip, sub-project.zip > > > I have a parent project that has a site descriptor and a pom project that= has the parent project as parent. Neither of them defines the locales para= meter of the site plugin. > When I try to build the sub-project, I get an error that Maven cannot fin= d the site_en.xml descriptor of the parent project. Why doesn't it just use= the site.xml? -- This message was sent by Atlassian JIRA (v7.6.3#76005)