[jira] Updated: (MSITE-358) site.xml urls are not always correct

["Brian Fox (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MSITE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox updated MSITE-358:
----------------------------

         Priority: Blocker  (was: Major)
      Description: 
This is so completely broken that it must be fixed before another release occurs. 

The maven-parent site.xml defines some images as:
{noformat}
  <bannerLeft>
    <name>${project.name}</name>
    <src>http://maven.apache.org/images/apache-maven-project-2.png</src>
    <href>http://maven.apache.org/</href>
  </bannerLeft>
  <bannerRight>
    <src>http://maven.apache.org/images/maven-logo-2.gif</src>
  </bannerRight>
{noformat}

The site plugin somewhere along the line replaces these urls with ../../ repeated based on how far down the inheritence tree you are from maven-parent. This means you can't stage or deploy a site to a different location than the maven-parent because all urls will point back to maven-parent's /images. Worse, every module has its own copy of the css and images so there's no reason for it to depend on the parent at all.

  was:It appears that when trying to deploy or stage a site, the plugin is calculating the relative path to the images. If the location you stage the site is not the same number of folders deep as the final deployment, then when you move the site, the images will all be broken.

    Fix Version/s: 2.0-beta-8
          Summary: site.xml urls are not always correct  (was: skin urls are not always correct)

> site.xml urls are not always correct
> ------------------------------------
>
>                 Key: MSITE-358
>                 URL: http://jira.codehaus.org/browse/MSITE-358
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-6
>            Reporter: Brian Fox
>            Priority: Blocker
>             Fix For: 2.0-beta-8
>
>
> This is so completely broken that it must be fixed before another release occurs. 
> The maven-parent site.xml defines some images as:
> {noformat}
>   <bannerLeft>
>     <name>${project.name}</name>
>     <src>http://maven.apache.org/images/apache-maven-project-2.png</src>
>     <href>http://maven.apache.org/</href>
>   </bannerLeft>
>   <bannerRight>
>     <src>http://maven.apache.org/images/maven-logo-2.gif</src>
>   </bannerRight>
> {noformat}
> The site plugin somewhere along the line replaces these urls with ../../ repeated based on how far down the inheritence tree you are from maven-parent. This means you can't stage or deploy a site to a different location than the maven-parent because all urls will point back to maven-parent's /images. Worse, every module has its own copy of the css and images so there's no reason for it to depend on the parent at all.

-- 
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