maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <>
Subject [jira] Updated: (MSITE-535) Do not use project.url for relative link resolution
Date Wed, 16 Mar 2011 20:19:24 GMT


Dennis Lundberg updated MSITE-535:

    Fix Version/s: 3.0-beta-4
          Summary: Do not use project.url for relative link resolution  (was: Do not use project.url
for relativ link resolution)

> Do not use project.url for relative link resolution
> ---------------------------------------------------
>                 Key: MSITE-535
>                 URL:
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Improvement
>          Components: doxia integration, inheritance, relative links
>    Affects Versions: 2.2
>            Reporter: Lukas Theussl
>            Assignee: Lukas Theussl
>             Fix For: 2.3, 3.0-beta-4
> IMO should be used instead. Imagine a multi-module site
with a distributionManagement url that points to the local file system. A local deploy will
move any child sites to sub-directories of the parent (by default), but if you forget to adjust
the project urls for all children, the relative links are all wrong because they are calculated
from the project urls. There are numerous examples and JIRAs where people are confused about
this. Having to specify a url for each single child project is a duplicate information and
is also logically not necessary. Note that the distributionManagement url always exists (otherwise
the deploy will fail), while the project url is optional. IMO the project url should not be
used for the local site generation at all, it is just a piece of user information.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message