[
http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103012
]
John Allen edited comment on MSITE-159 at 7/23/07 12:48 PM:
------------------------------------------------------------
IMHO a project.URL is supposed to point to the web accessible location for that
project and thus yes there is tight coupling between the
distroManagement.site.url and the project.URL. If one wants to redirect/map via
web mechanism the project.URL to some other web location then that's fine too.
(i.e. redirect your htdocs requests to htdocs/site)
Re isnt that why you define them as absolute? Well yes but also not really, a
project's URL is absolute as it is its published external web address
accessible from anywhere for that artifact. I can depend on your project and
will want to link to its web materials. If you made your sub-modules use
explicitly defined relative URLs then they would never be accessible to anyone
other than your related site pages (ie parent/children).
Re offline - We find it easier to generate our offline docs using these
auto-generated relative URLs, we get a sompletely self referential site and the
browser doesnt try and jump online all the time.
I expect the real answer to these 'i dont like', 'i do like' issues with
relative URLs is to make it a configuration option :)
was:
Re isnt that why you define them as absolute? Well yes but also not really, a
project's URL is absolute as it is its published external web address
accessible from anywhere. I can depend on your project and will want to link to
it and will need this to see your site. If you made your sub-modules use
explicitly defined relative URLs then they would never be accessible to anyone
other than your related site pages (ie parent/children). We find it easier to
generate our offline docs using relatives as well via the site:stage mojo -
this lets us create a completely self referential site without having the
browser try and jump online all the time.
I expect the real answer to these 'i dont like', 'i do like' issues with
relative URLs is to make it a configuration option :)
> 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
