[
http://jira.codehaus.org/browse/MSITE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-322:
--------------------------------
Fix Version/s: 2.3
I agree, the deploy mojo should be modified to deploy different language sites
separately.
> problem with internationalization of multimodule projects
> ----------------------------------------------------------
>
> Key: MSITE-322
> URL: http://jira.codehaus.org/browse/MSITE-322
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: internationalization
> Affects Versions: 2.0-beta-5, 2.0-beta-6, 2.0-beta-7
> Reporter: Anne Gerodolle
> Fix For: 2.3
>
> Attachments: multilingue.zip
>
>
> When trying to internationalize a multimodule project, the "modules" menu
> does not work in alternate languages, and it is very difficult to build a
> consistent site in the non default language, with links working OK.
> e.g. in attached multilingue.zip example, if I run "mvn site" then "mvn
> site;deploy" , the "mymodule" link in fr/index.html refers to
> fr/mymodule/index.html, wehereas the corresponding page is deployed as
> "mymodule/fr/index.html" .
> I can think of 2 ways to solve this issues, one of them seems preferable :
> one is to correct the link so that it refers to "mymodule.fr.index.html"
> the second is to deploy the submodule localized version in fr/mymodule rather
> than in mymodule/fr . I think this solution is preferable, because it makes
> the localized site more readable. For example, if we want to create a link
> that refers to the parent module, with the first solution we should refer to
> "../../fr/index.html" whereas with the second we simply refer to ".."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
