From issues-return-136408-archive-asf-public=cust-asf.ponee.io@maven.apache.org Fri Aug 17 17:34: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 7172A18067A for ; Fri, 17 Aug 2018 17:34:04 +0200 (CEST) Received: (qmail 95191 invoked by uid 500); 17 Aug 2018 15:34: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 94963 invoked by uid 99); 17 Aug 2018 15:34:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2018 15:34:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id F4130C109E for ; Fri, 17 Aug 2018 15:34:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 2r3u6ZGCJAmv for ; Fri, 17 Aug 2018 15:34: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 6FCDF5F124 for ; Fri, 17 Aug 2018 15:34: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 A0F7DE02F1 for ; Fri, 17 Aug 2018 15:34: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 2636923F98 for ; Fri, 17 Aug 2018 15:34:00 +0000 (UTC) Date: Fri, 17 Aug 2018 15:34:00 +0000 (UTC) From: "Mykel Alvis (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MNGSITE-348) Multi-module builds staging uses "staging" for the first module and "Staging" for subsequent stagings 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/MNGSITE-348?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Mykel Alvis updated MNGSITE-348: -------------------------------- Description:=20 I have a project that is a hierarchical tree of parents (i..e everything is= a "pom" type). Only the=C2=A0root project has a nexus [https://artifacts.example.io/repository/sites/DELETE/io.example/exam= ple-parent-support/25-SNAPSHOT/] and all sub-modules=C2=A0are intended to=C2=A0inherit the "standard" site s= tructure based on the fact that module names are the same as the artifact i= dentifier. No config has a topSiteURL set Current config of the site plugin is as follows (but has been juggled many = times with equivalent results): {quote}=C2=A0 org.apache.maven.plugins maven-site-plugin ${maven.site.plugin.version} org.apache.maven.doxia doxia-site-renderer 1.8.1 org.apache.maven.doxia doxia-module-markdown 1.8 compile org.apache.maven.doxia doxia-module-fml 1.8 compile org.apache.maven.doxia doxia-module-latex 1.8 compile org.apache.maven.doxia doxia-module-apt 1.8 compile org.apache.maven.doxia doxia-module-xdoc 1.8 compile org.apache.maven.wagon wagon-webdav-jackrabbit 3.1.0 compile {quote} =C2=A0 =C2=A0 site:site works essentially as-expected. site:stage does something totally weird.=C2=A0=C2=A0 {{mvn site:stage}} {{[INFO] Scanning for projects...}} {{[INFO] -----------------------------------------------------------------= -------}} {{[INFO] Reactor Build Order:}} {{[INFO] }} {{[INFO] example-parent-support [pom]}} {{[INFO] example-parent-minimal [pom]}} {{[INFO] example-oss-root [pom]}} {{.}} {{.}} {{.}} {{.}} {{[INFO] }} {{[INFO] ----------------< io.example:example-parent-support >------------= -----}} {{[INFO] Building example-parent-support 25-SNAPSHOT [1/10]}} {{[INFO] --------------------------------[ pom ]--------------------------= -------}} {{[INFO]}} {{[INFO] =E2=80=94 maven-site-plugin:3.7.1:stage (default-cli) @ example-p= arent-support ---}} {{[INFO] Using this base directory for staging: /home/mykel.alvis/git/exam= ple-parent-support/target/staging}} {{[INFO] Pushing /home/mykel.alvis/git/example-parent-support/target/site}= } {{[INFO] >>> to [file:///home/mykel.alvis/git/example-parent-support/targe= t/staging/./|file:///home/mykel.alvis/git/example-parent-support/target/sta= ging/]}} {{[INFO] }} {{[INFO] ----------------< io.example:example-parent-minimal >------------= -----}} {{[INFO] Building example-parent-minimal 25-SNAPSHOT [2/10]}} {{[INFO] --------------------------------[ pom ]--------------------------= -------}} {{[INFO] }} {{[INFO] =E2=80=94 maven-site-plugin:3.7.1:stage (default-cli) @ example-p= arent-minimal ---}} {{[INFO] Using this base directory for staging: /home/mykel.alvis/git/exam= ple-parent-support/example-parent-minimal/target/Staging}} {{[INFO] Pushing /home/mykel.alvis/git/example-parent-support/example-pare= nt-minimal/target/site}} {{[INFO] >>> to [file:///home/mykel.alvis/git/example-parent-support/examp= le-parent-minimal/target/Staging/../../../DELETE/io.example/example-parent-= support/25-SNAPSHOT/example-parent-minimal|file:///home/mykel.alvis/git/exa= mple-parent-support/DELETE/io.example/example-parent-support/25-SNAPSHOT/ex= ample-parent-minimal]}} {{[INFO]}}{{=C2=A0}} =C2=A0 Note that the first target was {{target/staging}} and the second was {{target/Staging}} What's up with that?=C2=A0 It appears to be causing staging to fail, and I've been live-debugging mave= n site runs for 3 days trying to spot where the "staging" -> "Staging" change occurs, but so far all I can tell is that the LifecycleModuleBuilder= (and/or something above it inthe call chain) is supplying the subsequent i= terations of the plugin execution from the reactor with `...target/Staging`= somehow.=C2=A0 I just don't know how because single-stepping through maven= is somewhat like getting caught in a maze of twisty passages, all alike. I accept (somewhat) that some people consider sites=C2=A0as second-class ci= tizens outside of plugins, but I really want them to work correctly.=C2=A0 = Audits go a lot easier with good docs. =C2=A0 =C2=A0 was: I have a project that is a hierarchical tree of parents (i..e everything is= a "pom" type). Only the=C2=A0root project has a nexus https://artifacts.example.io/repository/sites/DELETE/io.example/examp= le-parent-support/25-SNAPSHOT/ and all sub-modules=C2=A0are intended to=C2=A0inherit the "standard" site s= tructure based on the fact that module names are the same as the artifact i= dentifier. No config has a topSiteURL set Current config of the site plugin is as follows (but has been juggled many = times with equivalent results): {{ }} {{ org.apache.maven.plugins}} {{ maven-site-plugin}} {{ 3.7.1}} {{ }} {{ }} {{ }} {{ }} {{ org.apache.maven.doxia}} {{ doxia-site-renderer}} {{ 1.8.1}} {{ }} {{ }} {{ org.apache.maven.doxia}} {{ doxia-module-markdown}} {{ 1.8}} {{ compile}} {{ }} {{ }} {{ org.apache.maven.doxia}} {{ doxia-module-fml}} {{ 1.8}} {{ compile}} {{ }} {{ }} {{ org.apache.maven.doxia}} {{ doxia-module-latex}} {{ 1.8}} {{ compile}} {{ }} {{ }} {{ org.apache.maven.doxia}} {{ doxia-module-apt}} {{ 1.8}} {{ compile}} {{ }} {{ }} {{ org.apache.maven.doxia}} {{ doxia-module-xdoc}} {{ 1.8}} {{ compile}} {{ }} {{ }} {{ org.apache.maven.wagon}} {{ wagon-webdav-jackrabbit}} {{ 3.1.0}} {{ compile}} {{ }} {{ }} {{ }} =C2=A0 =C2=A0 site:site works essentially as-expected. site:stage does something totally weird.=C2=A0=C2=A0 {{mvn site:stage}} {{[INFO] Scanning for projects...}} {{[INFO] ------------------------------------------------------------------= ------}} {{[INFO] Reactor Build Order:}} {{[INFO] }} {{[INFO] example-parent-support [pom]}} {{[INFO] example-parent-minimal [pom]}} {{[INFO] example-oss-root [pom]}} {{.}} {{.}} {{.}} {{.}} {{[INFO] }} {{[INFO] ----------------< io.example:example-parent-support >-------------= ----}} {{[INFO] Building example-parent-support 25-SNAPSHOT [1/10]}} {{[INFO] --------------------------------[ pom ]---------------------------= ------}} {{[INFO]}} {{[INFO] --- maven-site-plugin:3.7.1:stage (default-cli) @ example-parent-s= upport ---}} {{[INFO] Using this base directory for staging: /home/mykel.alvis/git/examp= le-parent-support/target/staging}} {{[INFO] Pushing /home/mykel.alvis/git/example-parent-support/target/site}} {{[INFO] >>> to file:///home/mykel.alvis/git/example-parent-support/target/= staging/./}} {{[INFO] }} {{[INFO] ----------------< io.example:example-parent-minimal >-------------= ----}} {{[INFO] Building example-parent-minimal 25-SNAPSHOT [2/10]}} {{[INFO] --------------------------------[ pom ]---------------------------= ------}} {{[INFO] }} {{[INFO] --- maven-site-plugin:3.7.1:stage (default-cli) @ example-parent-m= inimal ---}} {{[INFO] Using this base directory for staging: /home/mykel.alvis/git/examp= le-parent-support/example-parent-minimal/target/Staging}} {{[INFO] Pushing /home/mykel.alvis/git/example-parent-support/example-paren= t-minimal/target/site}} {{[INFO] >>> to file:///home/mykel.alvis/git/example-parent-support/example= -parent-minimal/target/Staging/../../../DELETE/io.example/example-parent-su= pport/25-SNAPSHOT/example-parent-minimal}} {{[INFO]}}{{=C2=A0}} =C2=A0 Note that the first target was {{target/staging}} and the second was {{target/Staging}} What's up with that?=C2=A0 It appears to be causing staging to fail, and I've been live-debugging mave= n site runs for 3 days trying to spot where the "staging" -> "Staging" change occurs, but so far all I can tell is that the LifecycleModuleBuilder= (and/or something above it inthe call chain) is supplying the subsequent i= terations of the plugin execution from the reactor with `...target/Staging`= somehow.=C2=A0 I just don't know how because single-stepping through maven= is somewhat like getting caught in a maze of twisty passages, all alike. I accept (somewhat) that some people consider sites=C2=A0as second-class ci= tizens outside of plugins, but I really want them to work correctly.=C2=A0 = Audits go a lot easier with good docs. =C2=A0 =C2=A0 > Multi-module builds staging uses "staging" for the first module and "Stag= ing" for subsequent stagings > -------------------------------------------------------------------------= ---------------------------- > > Key: MNGSITE-348 > URL: https://issues.apache.org/jira/browse/MNGSITE-348 > Project: Maven Project Web Site > Issue Type: Bug > Environment: Case-sensitive filesystems (i.e. unix-like, primaril= y) with maven 3.5.4 > Reporter: Mykel Alvis > Priority: Major > > I have a project that is a hierarchical tree of parents (i..e everything = is a "pom" type). > Only the=C2=A0root project has a > > nexus > [https://artifacts.example.io/repository/sites/DELETE/io.example/ex= ample-parent-support/25-SNAPSHOT/] > > and all sub-modules=C2=A0are intended to=C2=A0inherit the "standard" site= structure based on the fact that module names are the same as the artifact= identifier. > No config has a topSiteURL set > Current config of the site plugin is as follows (but has been juggled man= y times with equivalent results): > {quote}=C2=A0 > org.apache.maven.plugins > maven-site-plugin > ${maven.site.plugin.version} > > > > > org.apache.maven.doxia > doxia-site-renderer > 1.8.1 > > > org.apache.maven.doxia > doxia-module-markdown > 1.8 > compile > > > org.apache.maven.doxia > doxia-module-fml > 1.8 > compile > > > org.apache.maven.doxia > doxia-module-latex > 1.8 > compile > > > org.apache.maven.doxia > doxia-module-apt > 1.8 > compile > > > org.apache.maven.doxia > doxia-module-xdoc > 1.8 > compile > > > org.apache.maven.wagon > wagon-webdav-jackrabbit > 3.1.0 > compile > > > > {quote} > =C2=A0 > =C2=A0 > site:site works essentially as-expected. > site:stage does something totally weird.=C2=A0=C2=A0 > {{mvn site:stage}} > {{[INFO] Scanning for projects...}} > {{[INFO] ---------------------------------------------------------------= ---------}} > {{[INFO] Reactor Build Order:}} > {{[INFO] }} > {{[INFO] example-parent-support [pom]}} > {{[INFO] example-parent-minimal [pom]}} > {{[INFO] example-oss-root [pom]}} > {{.}} > {{.}} > {{.}} > {{.}} > {{[INFO] }} > {{[INFO] ----------------< io.example:example-parent-support >----------= -------}} > {{[INFO] Building example-parent-support 25-SNAPSHOT [1/10]}} > {{[INFO] --------------------------------[ pom ]------------------------= ---------}} > {{[INFO]}} > {{[INFO] =E2=80=94 maven-site-plugin:3.7.1:stage (default-cli) @ example= -parent-support ---}} > {{[INFO] Using this base directory for staging: /home/mykel.alvis/git/ex= ample-parent-support/target/staging}} > {{[INFO] Pushing /home/mykel.alvis/git/example-parent-support/target/sit= e}} > {{[INFO] >>> to [file:///home/mykel.alvis/git/example-parent-support/tar= get/staging/./|file:///home/mykel.alvis/git/example-parent-support/target/s= taging/]}} > {{[INFO] }} > {{[INFO] ----------------< io.example:example-parent-minimal >----------= -------}} > {{[INFO] Building example-parent-minimal 25-SNAPSHOT [2/10]}} > {{[INFO] --------------------------------[ pom ]------------------------= ---------}} > {{[INFO] }} > {{[INFO] =E2=80=94 maven-site-plugin:3.7.1:stage (default-cli) @ example= -parent-minimal ---}} > {{[INFO] Using this base directory for staging: /home/mykel.alvis/git/ex= ample-parent-support/example-parent-minimal/target/Staging}} > {{[INFO] Pushing /home/mykel.alvis/git/example-parent-support/example-pa= rent-minimal/target/site}} > {{[INFO] >>> to [file:///home/mykel.alvis/git/example-parent-support/exa= mple-parent-minimal/target/Staging/../../../DELETE/io.example/example-paren= t-support/25-SNAPSHOT/example-parent-minimal|file:///home/mykel.alvis/git/e= xample-parent-support/DELETE/io.example/example-parent-support/25-SNAPSHOT/= example-parent-minimal]}} > {{[INFO]}}{{=C2=A0}} > =C2=A0 > Note that the first target was > {{target/staging}} > and the second was > {{target/Staging}} > What's up with that?=C2=A0 > It appears to be causing staging to fail, and I've been live-debugging ma= ven site runs for 3 days trying to spot where the > "staging" -> "Staging" > change occurs, but so far all I can tell is that the LifecycleModuleBuild= er (and/or something above it inthe call chain) is supplying the subsequent= iterations of the plugin execution from the reactor with `...target/Stagin= g` somehow.=C2=A0 I just don't know how because single-stepping through mav= en is somewhat like getting caught in a maze of twisty passages, all alike. > I accept (somewhat) that some people consider sites=C2=A0as second-class = citizens outside of plugins, but I really want them to work correctly.=C2= =A0 Audits go a lot easier with good docs. > =C2=A0 > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)