[
http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123756
]
Kay Grosskop commented on MSITE-159:
------------------------------------
(John, sorry for my late reaction.)
You are right: the internal references of the generated site should work
wherever its build. Thats why the url's should be relative there.
BUT: in the example above the point to use an absolute url is, that it refers
to an EXTERNAL resource (https://bla.mycomp.nl/docs). Since this resource
happens to have the same base url than the site deployment url, maven thinks
that it should be treated as relative.
I agree with Ramon, that maven should not override well established conventions
here just to correct wrong configuration (people using absolute url's in the
site descriptors where they should use relatives).
Also I did not say that the project's main site url should be relative.
What would the configuration option be here? 'interpret ALL absolute url's with
the same base-url as the site root as relative url's' ?
Correct me if I didn't get what you commented.
> 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
> Components: relative links
> 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
