Maven 2.x and 3.x Site Plugin

Broken links to submodules when staging site

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-6
  • Fix Version/s: 2.0-beta-7
  • Component/s: multi module, relative links
  • Labels:
    None
  • Environment:
    Linux
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

The attached testcase has a broken link when staged, and the relative path to it looks horrible.

I had assumed that recent development in maven-doxia-tools might have been to address this issue, so I tried to reproduce with the latest SVN version. There I hit MSITE-315, so I'm reporting this for 2.0-beta-6 as well.

You might want to make a staging testcase out of this, and have links checked. I don't yet understand all the magic behind the integration tests, so I didn't provide a patch for this.

Issue Links

This issue is duplicated by:
MSITE-321 multi module, hierarichal project broken link in site and site:stage Major Closed
This issue is related to:
MSITE-275 site:stage for multimodule project creates wrong links Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dennis Lundberg added a comment -

The ugly relative paths are tracked by MSITE-275

Show
Dennis Lundberg added a comment - The ugly relative paths are tracked by MSITE-275
Hide
Permalink
Dennis Lundberg added a comment -

Fixed in r664376.
New 2.0-beta-7-SNAPSHOT deployed.
Please verify.

Show
Dennis Lundberg added a comment - Fixed in r664376. New 2.0-beta-7-SNAPSHOT deployed. Please verify.
Hide
Permalink
Martin von Gagern added a comment -

While 2.0-beta-7-SNAPSHOT as of r664376 does place child sites in the correct directory, the links to submodules are still broken here. In that respect, this issue has not really been fixed. On the other hand, MSITE-275 describes links that are not only ugly but seem to be broken in just the way my links are, so this here might be a duplicate of MSITE-275.

When running the test case in a directory /home/mvg/src/java/parent where /home/mvg is my home directory, I get this behaviour:
~/src/java/parent> mvn
...
Using this directory for staging: /home/mvg/src/java/parent/target/staging
...
Using this directory for staging: /home/mvg/src/java/parent/target/staging
...
~/src/java/parent> grep Child target/staging/ssh.example.com/htdocs/parent/index.html
<a href="../../home/mvg/src/java/parent/../../../ssh.example.com/htdocs/parent">Child</a>

Adding some more debug code to 2.0-beta-8-SNAPSHOT r672745 I find that outputRelativePath is "../../.." for the parent and "../../../.." for the child project.

Show
Martin von Gagern added a comment - While 2.0-beta-7-SNAPSHOT as of r664376 does place child sites in the correct directory, the links to submodules are still broken here. In that respect, this issue has not really been fixed. On the other hand, MSITE-275 describes links that are not only ugly but seem to be broken in just the way my links are, so this here might be a duplicate of MSITE-275. When running the test case in a directory /home/mvg/src/java/parent where /home/mvg is my home directory, I get this behaviour: ~/src/java/parent> mvn ... Using this directory for staging: /home/mvg/src/java/parent/target/staging ... Using this directory for staging: /home/mvg/src/java/parent/target/staging ... ~/src/java/parent> grep Child target/staging/ssh.example.com/htdocs/parent/index.html <a href="../../home/mvg/src/java/parent/../../../ssh.example.com/htdocs/parent">Child</a> Adding some more debug code to 2.0-beta-8-SNAPSHOT r672745 I find that outputRelativePath is "../../.." for the parent and "../../../.." for the child project.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.