Hi, Sergio Fernández <wik...@apache.org> schrieb am Do., 17. Nov. 2016 um 00:46 Uhr:
> I believe with f6a80e6fcd39a8ee7426826e7b25e5cfe0628820 we've fixed the > COMMONSRDF-50 issue: > > > https://git1-us-west.apache.org/repos/asf?p=incubator-commonsrdf.git;a=commitdiff;h=f6a80e6fcd39a8ee7426826e7b25e5cfe0628820;hp=b05e3e6e6acad0baeeb7e19358093232119548bb > > At list for the the result at target/staging looks good when executing: mvn > clean site site:stage > > Please Stian, take a look to double check it. > Our documentation [1] says mvn clean site site:stage scm-publish:publish-scm will do the trick. If that doesn't work, we should fix the docs. Benedikt [1] http://commons.apache.org/site-publish.html > > Cheers, > > > On Thu, Nov 17, 2016 at 12:25 AM, Gilles <gil...@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-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 6602747925 <+43%20660%202747925> > e: sergio.fernan...@redlink.co > w: http://redlink.co >