MSITE-820 created but this will be for maven-site-plugin 3.8 Regards,
Hervé [1] https://issues.apache.org/jira/browse/MSITE-820 Le lundi 23 avril 2018, 20:18:34 CEST Piergiorgio Lucidi a écrit : > Hi Hervé, > > thank you so much for your support. > > Probably the best way is to keep the same definition that we need to > specify in the maven-site-plugin, I mean zh_CN for folders and definitions. > In this way it will be more easier for anyone to specify the same locale > set in the pom.xml. > > I have tried your fix and it works very well :) > Thank you again and I'll wait for the next release and eventually I'll > change the folders layout to be consistent with the extended version of the > locale. > > Cheers, > PJ > > 2018-04-23 18:40 GMT+02:00 Hervé BOUTEMY <[email protected]>: > > Hi, > > > > I had a look at your code: very interesting, I'm glad to be able to help > > such > > a use case. > > > > You found a bug in site:run MSITE-818 [1] that I fixed quickly (stupid > > inconsistency) > > > > but I need your help to decide what to do really since I fear our current > > maven-site-plugin choice is not the right one (and that caused the > > inconsistency). > > This has to do with the fact that zh_CN locale contains not only a > > language > > (zh) but also a country (region) (CN): but the path in the generated html > > is > > build only from language (/zh/), even if the source directory was the full > > locale (/zh_CN/), be it for site:site or site:run > > > > Question: shouldn't maven-site-plugin keep the full locale for directory? > > then have generated html in /zh_CN/? Or is it really a good idea to keep > > generated html in /zh/? > > > > to be consistent, I would have expected that since source is in > > src/site/zh_CN > > generated content would go to target/site/zh_CN, not target/site/zh/ as > > currently... > > > > At least now, you can build maven-site-plugin 3.7.1-SNAPSHOT for yourself > > and > > site:run will work: I expect to do a release soon, since it contains > > important > > fixes from 3.7, then I'm eager to have your feedback > > > > Changing output html directory from zh to zh_CN would go in another > > release, > > since it's a more important change than the simple bugfix that 3.7.1 is > > expected to be > > > > A little hint on your site: you don't need to configure Markdown Doxia > > parser, > > it is enabled by default since a long time > > > > Regards, > > > > Hervé > > > > > > [1] https://issues.apache.org/jira/browse/MSITE-818 > > > > Le lundi 23 avril 2018, 11:20:26 CEST Piergiorgio Lucidi a écrit : > > > Hi all, > > > > > > we are working on our brand new website but we have an issue using the > > > Doxia Plugin. > > > > > > ManifoldCF website supports three different languages: english, japanese > > > and chinese [1]. > > > > > > We are trying to build the new website using Maven Site Plugin with > > > Doxia > > > and the Fluido skin using markdown templates. You can take a look at our > > > current state in our issue in JIRA [2]. > > > > > > Actually we have a first sprint of this development [3], where the > > > > english > > > > > language is configured as the default one and then we have added > > > japanese > > > and chinese as new locales. > > > > > > We have a problem when trying to get the content using the chinese > > > locale > > > because the website is returning the following exception: > > > > > > HTTP ERROR 500 > > > > > > Problem accessing /zh/index.html. Reason:{{ No doxia bean found for the > > > locale zh_CN}} > > > > > > Caused by:{{javax.servlet.ServletException: No doxia bean found for the > > > locale zh_CN at > > > org.apache.maven.plugins.site.run.DoxiaFilter.doFilter( > > > > DoxiaFilter.java:129) > > > > > at > > > org.mortbay.jetty.servlet.ServletHandler$CachedChain. > > > > doFilter(ServletHandler > > > > > .java:1157) at > > > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) > > > > at > > > > > org.mortbay.jetty.security.SecurityHandler.handle( > > > > SecurityHandler.java:216) > > > > > at org.mortbay.jetty.servlet.SessionHandler.handle( > > > > SessionHandler.java:182) > > > > > at org.mortbay.jetty.handler.ContextHandler.handle( > > > > ContextHandler.java:765) > > > > > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440) > > > > at > > > > > org.mortbay.jetty.handler.HandlerCollection.handle( > > > > HandlerCollection.java:11 > > > > > 4) at > > > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > > > > at > > > > > org.mortbay.jetty.Server.handle(Server.java:326) at > > > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > > > > at > > > > > org.mortbay.jetty.HttpConnection$RequestHandler. > > > > headerComplete(HttpConnectio > > > > > n.java:926) at org.mortbay.jetty.HttpParser. > > > > parseNext(HttpParser.java:549) > > > > > at > > > org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at > > > org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at > > > > > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java: > > 410) > > > > > at > > > org.mortbay.thread.QueuedThreadPool$PoolThread. > > > > run(QueuedThreadPool.java:582 > > > > > ) }} > > > > > > > > > Do you have any ideas how to solve this problem? > > > > > > I'm wondering if there are some rules related to configure zh_CN inside > > > > the > > > > > pom with the related folders for contents. For Japanese I set ja as a > > > new > > > locale and then I have created a specific folder site/ja/markdown for > > > contents. > > > > > > The same I have done with Chinese but it seems something wrong for this > > > setting and with mvn site:run I have the following log: > > > > > > [INFO] ---------------------< org.apache.manifoldcf:site > > > > > > >--------------------- > > > > > > [INFO] Building ManifoldCF - Site 2.10-SNAPSHOT > > > [INFO] --------------------------------[ pom > > > ]--------------------------------- > > > [INFO] > > > [INFO] --- maven-site-plugin:3.7:run (default-cli) @ site --- > > > [INFO] Logging to org.slf4j.impl.MavenSimpleLogger(org.mortbay.log) via > > > org.mortbay.log.Slf4jLog > > > [INFO] Relativizing decoration links with respect to localized project > > > > URL: > > > http://www.apache.org/mcf-parent/site/ > > > [INFO] Rendering site with org.apache.maven.skins:maven- > > > > fluido-skin:jar:1.7 > > > > > skin. > > > [INFO] Relativizing decoration links with respect to localized project > > > > URL: > > > http://www.apache.org/mcf-parent/site/ > > > [INFO] Rendering site with org.apache.maven.skins:maven- > > > > fluido-skin:jar:1.7 > > > > > skin. > > > [INFO] Relativizing decoration links with respect to localized project > > > > URL: > > > http://www.apache.org/mcf-parent/site/ja > > > [INFO] Rendering site with org.apache.maven.skins:maven- > > > > fluido-skin:jar:1.7 > > > > > skin. > > > [INFO] Relativizing decoration links with respect to localized project > > > > URL: > > > http://www.apache.org/mcf-parent/site/ja > > > [INFO] Rendering site with org.apache.maven.skins:maven- > > > > fluido-skin:jar:1.7 > > > > > skin. > > > [INFO] Relativizing decoration links with respect to localized project > > > > URL: > > > http://www.apache.org/mcf-parent/site/zh > > > [INFO] Rendering site with org.apache.maven.skins:maven- > > > > fluido-skin:jar:1.7 > > > > > skin. > > > [INFO] Relativizing decoration links with respect to localized project > > > > URL: > > > http://www.apache.org/mcf-parent/site/zh > > > [INFO] Rendering site with org.apache.maven.skins:maven- > > > > fluido-skin:jar:1.7 > > > > > skin. > > > [INFO] Starting Jetty on http://localhost:8080/ > > > [INFO] jetty-6.1.25 > > > [INFO] NO JSP Support for /, did not find > > > org.apache.jasper.servlet.JspServlet > > > [INFO] Started [email protected]:8080 > > > > > > > > > Thank you for your support. > > > > > > Regards, > > > PJ > > > > > > [1] - http://manifoldcf.apache.org/ > > > [2] - https://issues.apache.org/jira/browse/CONNECTORS-1495 > > > [3] - > > > https://svn.apache.org/repos/asf/manifoldcf/site/branches/ > > > > CONNECTORS-1495/ > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
