[
http://jira.codehaus.org/browse/MSITE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253388#action_253388
]
Stefan Hansel commented on MSITE-227:
-------------------------------------
Hi Lukas,
I'm still struggling with this one and I'm happy to accept any workaround
possible.
My main goal is just get a report, where childs and masters are linked with
relative links (based on the demo project attached here).
The distribution URL is configured in the settings.xml of our buildserver, I
have no influence on it. But I can use any url that helps in the project's pom.
As our buildserver then takes the generated sites and puts them somewhere on
the webserver relative to the current build number it's important, that the
final reports only have relative URLs.
I tried different things now in the url-tags of parent and child, but nothing
gives my any succes:
A) your proposed solution:
parent: <url>file:///tmp/MSITE-227/</url>
child: <url>file:///tmp/module1/</url>
distribution: <url>file:///buildXYZ</url>
=> give absolute links from parent to child and from child to parent => not
working for me
B) relative pathes 1
parent: <url>.</url>
child: <url>./module1</url>
distribution: <url>file:///buildXYZ</url>
=> creates only relative links between parent + childs.
Unfortunately expects a folder structure, where module1 is withing the parent
folder.
But all reports are generated in the same folder (flat structure), so the links
are not working.
If I could manipulate the site-deploy target to create a nested folder
structure, this would work.
C) relative pathes 2
parent: <url>.</url>
child: <url>./../module1</url>
distribution: <url>file:///buildXYZ</url>
parent to child link is relative and working
child to parent link is relative but not working ("../../../index.html" instead
of "../MSITE-227/index.html")
If the created folder structure wasn't flat (i.e. every project in the same
folder opposed to having the childs below the parent) then solution (B) what be
what I wanted.
This folder structure is already created when artifactID!=foldername but I
cannot use this because either I had to rename my VCS-Project names to
something strange or I had to rename the artifactID to something strange.
I cannot believe that I'm the first one how wants to create multimodule sites
with only relative links to be copied by the buildserver to some other (maven
independent) location.
> 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
