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

Lukas Theussl commented on MSITE-227:
-------------------------------------

I'm not following your points above. If you cannot use absolute URLs and you 
cannot use relative URLs, then what would you like to use? The point is that in 
general single modules can be deployed to different locations than what is 
given by their relative source location. Their final relative locations are 
determined by the url elements in the poms, as that's where the single sites 
are supposed to end up at. This is 
[documented|http://maven.apache.org/plugins/maven-site-plugin/faq.html#Use_of_url]
 and that's the way it is currently supposed to work. (As a side note, I agree 
that it shouldn't be like that, see MSITE-535)

> 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

        

Reply via email to