[jira] Commented: (MSITE-227) site:deploy -> wrong links in ${modules} when artifactId=module's directory

["Stefan Hansel (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MSITE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249903#action_249903 ] 

Stefan Hansel commented on MSITE-227:
-------------------------------------

I have to kindly disagree.

1) I cannot use absolute URLs in the modules, as this would bind my build to a specific environment. I couldn't run it on my workstation and on the buildserver with the same POM.

2) I cannot use relative URLs. What about projects with multiple layers
A
  -> B
      --> C
      --> D
  ->  E

I want to be able to run a multimodule site for project A and B. If I have to use relative pathes this would work :(

In a multimodule build I want to be able to run a full report, but single developers should also be able to run a report just for a single project.

3) The multimodule site should work out of the box. This bug is the biggest problem a had (and still have) with maven since I started with maven3 a month ago. 
It took me three days to find out what the reason was.

4) Why is it working (out of the box), when the artifactID is different to the directory-anme?
Quoting from the original report: 
{quote}
The weirdest thing is that everything is fine when the artefactId and the eclipse project name (directory) are different !!! the problem appears only when they are identical.
{quote}
I can confirm that just using different artifactIDs workarounds this problem.



I don't see any reason, why the site plugin shouldn't be able to create correct links in a multimodule setups without any workaround?

Please reopen this bug report.

> site:deploy -> wrong links in ${modules} when artifactId=module's directory
> ---------------------------------------------------------------------------
>
>                 Key: MSITE-227
>                 URL: http://jira.codehaus.org/browse/MSITE-227
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: multi module
>    Affects Versions: 2.0-beta-5, 2.0
>         Environment: Eclipse IDE
>            Reporter: Guimiot Isabelle
>            Assignee: Lukas Theussl
>         Attachments: MSITE-227-working.zip, MSITE-227.zip
>
>
> I have a problem in the ${modules} part when I run the site:deploy goal.
> my project contains a root module and 2 sub-modules, at the same directory depth (I'm using Eclipse) :
> workspace/myRoot/
> workspace/myModule1/
> workspace/myModule2/
> my root pom contains this module declaration :
> <modules>
> 	<module>../myModule1</module>
> 	<module>../myModule1</module>
> </modules>
> the site:deploy goal gives this structure :
> [deploydir]/myRoot/index.html --> root's index
> [deploydir]/myRoot/myModule1/index.html --> first module's index
> [deploydir]/myRoot/myModule2/index.html --> second module's index
> when the project name (directory name in the workspace) and the artifactId are exactly the same, I have wrong links, both in root and in sub-modules pages :
> - in the root page, my links to submodules are like this :
> <h5>Modules</h5>
> <ul>     
>     <li class="none">
>        <a href="../myModule1/index.html">myModule1</a> <!-- should be "myModule1/index.html" instead -->
>     </li>              
>     <li class="none">
>        <a href="../myModule2/index.html">myModule2</a> <!-- should be "myModule2/index.html" instead -->
>     </li>
> </ul>
> - and in both modules pages, my link to the parent project is like this :
> <h5>Parent project</h5>
> <ul>
>     <li class="none">
>        <a href="../myRoot/index.html">myRoot</a> <!-- should be "../index.html" instead -->
>     </li>
> </ul>
> The weirdest thing is that everything is fine when the artefactId and the eclipse project name (directory) are different !!! the problem appears only when they are identical...
> Thanks for your help !

-- 
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