[
http://jira.codehaus.org/browse/MSITE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103015
]
John Allen commented on MSITE-169:
----------------------------------
By default maven assumes that modules live under the parent project's
directory. And Jason is dead right, simply redeclare the correct URL and
distroManagement.site.utl info in all the projects to avoid this, in your case,
invalid assumption
> links to modules where not working if a modules dir is used
> -----------------------------------------------------------
>
> Key: MSITE-169
> URL: http://jira.codehaus.org/browse/MSITE-169
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4, 2.0-beta-5, 2.0-beta-6
> Reporter: Mathias Brökelmann
> Attachments: MNG-MSITE-169-maven-site-plugin.patch
>
>
> I've to place the modules into a separate directory:
> root/
> ..pom.xml
> ..modules/
> ....module1
> ....module2
> this is supported by maven through
> <modules>
> <module>modules/module1</module>
> <module>modules/module2</module>
> </modules>
> in pom.
> but the site generation seems to be broken:
> if mvn site-deploy is used the links to the modules contain
> modules/module1/index.html which is ok but unfortunately the generated site
> structure will be generated as follows:
> root/
> ..module1
> ..module2
> The result is that the links do not work.
> If I run mvn site-stage everything looks ok. The links doesn't contain
> modules dir anymore and eveything is working.
--
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
