Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.
Attachments
Issue Links
- depends upon
-
DOXIASITETOOLS-46 Separate inheritance assembling and link resolution
- Closed
-
MSHARED-189 DefaultSiteTool should not relativize links
- Closed
- is duplicated by
-
DOXIASITETOOLS-55 It does not appear to be possible to create an absolute link to a parent URL in a banner
- Closed
-
MSITE-254 Error when using an absolute URL in a menu item in site.xml
- Closed
-
MSITE-269 Urls rewritten when they contain the project urls' hostname
- Closed
-
MSITE-338 URLs in site.xml banner tags not rendered by site plugin if host not resolved by "nslookup"
- Closed
-
MSITE-468 Absolute links item href's are stripped to become relative
- Closed
-
MSITE-197 poweredBy Logo links don't work
- Closed
-
MSITE-229 Links in site.xml get translated to ../../../
- Closed
- is related to
-
MSITE-420 Parent project site descriptor menu options always a link back to parent site
- Closed
- relates to
-
MSITE-659 'relativizeDecorationLinks' relativizes too much.
- Closed
-
MSITE-62 make absolute paths relative where possible
- Closed