Return-Path: <dev-return-160324-archive-asf-public=cust-asf.ponee.io@commons.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 72B7A200BC2
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Thu, 17 Nov 2016 16:30:48 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 6F465160B0B; Thu, 17 Nov 2016 15:30:48 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 92274160AD8
	for <archive-asf-public@cust-asf.ponee.io>; Thu, 17 Nov 2016 16:30:47 +0100 (CET)
Received: (qmail 34125 invoked by uid 500); 17 Nov 2016 15:30:46 -0000
Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@commons.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@commons.apache.org>
List-Post: <mailto:dev@commons.apache.org>
List-Id: <dev.commons.apache.org>
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Delivered-To: mailing list dev@commons.apache.org
Received: (qmail 34112 invoked by uid 99); 17 Nov 2016 15:30:46 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2016 15:30:46 +0000
Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 0B5581A0046
	for <dev@commons.apache.org>; Thu, 17 Nov 2016 15:30:46 +0000 (UTC)
Received: by mail-wm0-f42.google.com with SMTP id a197so317520278wmd.0
        for <dev@commons.apache.org>; Thu, 17 Nov 2016 07:30:45 -0800 (PST)
X-Gm-Message-State: AKaTC00JUOQ0hVg0EMaZe0ruw+uUDd50DwD1tZDszS34WUswqc3pdSNtajTnGyI/zi805W3ysgTOV8cI2hDFOg==
X-Received: by 10.28.181.197 with SMTP id e188mr4696605wmf.32.1479396644641;
 Thu, 17 Nov 2016 07:30:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.168.137 with HTTP; Thu, 17 Nov 2016 07:30:24 -0800 (PST)
X-Originating-IP: [130.88.195.40]
In-Reply-To: <CAOfJQJ34RN2YHqqNcxne=a95K4E7Q6HJLRXvKdYR9wnDGLVmRw@mail.gmail.com>
References: <CAMBJEmXvJUVfxX65EarPq9F37oyy0uw9dum3xzuBeBdOz7R65w@mail.gmail.com>
 <fd28cd2cf092fd435e6574b35d04ef19@scarlet.be> <CAOfJQJ34RN2YHqqNcxne=a95K4E7Q6HJLRXvKdYR9wnDGLVmRw@mail.gmail.com>
From: Stian Soiland-Reyes <stain@apache.org>
Date: Thu, 17 Nov 2016 15:30:24 +0000
X-Gmail-Original-Message-ID: <CAMBJEmXZxXmO5Tcva0cyRr9OX==s9HjEqDiurd0nMvejpDJ9yQ@mail.gmail.com>
Message-ID: <CAMBJEmXZxXmO5Tcva0cyRr9OX==s9HjEqDiurd0nMvejpDJ9yQ@mail.gmail.com>
Subject: Re: How to publish multi-module site..?
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 17 Nov 2016 15:30:48 -0000

Thanks for having a go, Sergio!


I've tried it (after accidentally touching the live site) with the
corresponding staging SVN directory:

        <commons.scmPubUrl>https://svn.apache.org/repos/infra/websites/stag=
ing/commonsrdf/trunk/</commons.scmPubUrl>

(for test speed commented out all <module>s except api, using -pl api
would also work)


However deploying did not work for me:

   mvn clean site site:stage scm-publish:publish-scm

As it did not check in the sub-modules folders to SVN.

The top level target/staging/ do contain the correct sub-folders like
api/ and simple/ so they are easy enough to copy over manually to
target/site-content (where they are missing) - we can just complicate
our SITE.md with the manual cp and svn commands.



Neither did this work:

  mvn clean site site:stage site:deploy

(Same result)


Strangely I get log output like:

[INFO] Relativizing decoration links with respect to project URL:
https://commonsrdf.incubator.apache.org/commons-rdf-api/


..however the menu items are correctly going to /api/ - it's just that
api/ and simple/ etc. are not given to "svn add" and thus not checked
in.


Also svn is very slow to check in javadocs.. git2pub any day now please! :-=
)



On 16 November 2016 at 23:45, Sergio Fern=C3=A1ndez <wikier@apache.org> wro=
te:
> I believe with f6a80e6fcd39a8ee7426826e7b25e5cfe0628820 we've fixed the
> COMMONSRDF-50 issue:
>
> https://git1-us-west.apache.org/repos/asf?p=3Dincubator-commonsrdf.git;a=
=3Dcommitdiff;h=3Df6a80e6fcd39a8ee7426826e7b25e5cfe0628820;hp=3Db05e3e6e6ac=
ad0baeeb7e19358093232119548bb
>
> At list for the the result at target/staging looks good when executing: m=
vn
> clean site site:stage
>
> Please Stian, take a look to double check it.
>
> Cheers,
>
>
> On Thu, Nov 17, 2016 at 12:25 AM, Gilles <gilles@harfang.homelinux.org>
> wrote:
>
>> On Wed, 16 Nov 2016 11:26:41 +0000, Stian Soiland-Reyes wrote:
>>
>>> Hi, (in particular Gilles and Artem)
>>>
>>> What was the status of how to do a multi-site publish?  I just tried
>>> now for the Commons RDF 0.3.0 site, and I could not get it to work
>>> properly.
>>>
>>>
>>> As mentioned in
>>>
>>> http://central.maven.org/maven2/org/apache/commons/commons-
>>> parent/41/commons-parent-41.pom
>>> I added a <site>to <distributionManagement> using
>>> <url>scm:svn:${commons.scmPubUrl}</url>
>>>
>>>
>>> Note that as Commons RDF is still in the incubator (watch this space)
>>> it has a slightly different properties:
>>>
>>>
>>> <commons.scmPubUrl>https://svn.apache.org/repos/infra/websit
>>> es/production/commonsrdf/content/</commons.scmPubUrl>
>>>
>>>
>>> <commons.scmPubCheckoutDirectory>${project.build.directory}/
>>> site-content</commons.scmPubCheckoutDirectory>
>>>
>>>
>>> But I could not get it to publish the submodule sites correctly.
>>>
>>>
>>> mvn clean package site-deploy
>>>
>>>   overwrites the main site with the last module's site instead! (Do not
>>> use!)
>>>
>>>
>>>
>>>
>>> mvn clean package site scm-publish:publish-scm
>>>
>>> seems to work - but does not publish the sub-sites (e.g.
>>> commons-rdf-api/ subfolder)
>>>
>>>
>>> mvn clean package site site:stage scm-publish:publish-scm
>>>
>>> seems to have the same problem.
>>>
>>
>> In "Commons RNG" (most recent code is in branch "RNG-30__sampling"),
>> I've been using the following:
>>
>> $ mvn clean install site site:stage
>>
>> It creates the all the (sub-)sites in
>>   src/<module_name>/target
>> and concatenates them under
>>   src/target/staging
>> (in the top-level directory).
>>
>> The problem is that the above command creates a
>>   site-content
>> svn repository inside each module's directory that contains all the
>> (concatenated) web site; whereas IIUC that maven page:
>>   https://maven.apache.org/plugins/maven-site-plugin/examples/
>> multimodule.html
>> it should not be that way (since the "artefactId" and module directory
>> name _are_ the same).
>> IOW, why does maven automatically create the _sub_-site in each
>>   <module_name>/target/site
>> directory but does not copy its content under
>>   <module_name>/site-content/<module_name>/
>> ?
>>
>> I wonder why have a "site-content" under each
>>   <module_name>
>> directory, that would only duplicate whole (currently) or part of
>> the "top-level"
>>   site-content
>> ?
>>
>> Regards,
>> Gilles
>>
>>
>> And so I had to do this manual hack to afterwards add the submodules
>>> site folders to the SVN of the website:
>>>
>>> for a in api integration-tests jena jsonld-java rdf4j simple ;
>>>   do cp -r $a/target/site target/site-content/commons-rdf-$a ;
>>> done
>>>
>>> cd target/site-content/
>>> svn add commons-rdf-*
>>> svn commit -m "submodules"
>>>
>>>
>>> Any ideas..?
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> Sergio Fern=C3=A1ndez
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co



--=20
Stian Soiland-Reyes
http://orcid.org/0000-0001-9842-9718

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org