[ http://jira.codehaus.org/browse/MSITE-159?page=comments#action_80660 ] Kay Grosskop commented on MSITE-159: ------------------------------------
Moreover the current behaviour of the site generation leads to the following annoying issue: pom: <url>https://bla.mycomp.nl</url> <distributionManagement><site><url>scp://mycomp.nl/home/groups/bla/htdocs/site</url></site></distributionManagement> (where the project url is mapped to the htdocs directory) site.xml: <menu name="Docs"><item name="Document share" href="https://bla.mycomp.nl/docs"/> In this case, the it will create a relative link to href="docs". but since my site gets deployed in subdirectory ./site it will point erroneously to ./site/docs Now you can argue that the project-url is meant to point to the root of the site deployment location. But in my opinion absolute paths should stay absolute. Isn't that the reason why you define them absolute, because you want to overrule the relation with the deployment url? > Absolute URI rendered as relative URI if absolute URI related to domain of > POM URI > ---------------------------------------------------------------------------------- > > Key: MSITE-159 > URL: http://jira.codehaus.org/browse/MSITE-159 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Reporter: Ted Husted > > Under site-beta5 > if the POM references a URI like > <url>http://struts.apache.org</url> > absolute URLs used in the site.xml file are converted to relative references. > For example a reference to to "http://struts.apache.org/1.x"; becomes "1.x", > and a reference to > just "http://struts.apache.org"; becomes an empty string. > If the documentation is being used offline, there are many cases when we want > to refer people back to the website, to be sure the current information is > used. The best use case is a download page that determines the mirror via > CGI. > Another use case is referring to a sister site in the domain, that might > refer to another version. If used locally, the other site might not be in the > relative location. > Switching back to beta4 cures the behavior, and absolute URIs remain > absolute, as expected. -- 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
