[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171784#action_171784 ] 

murray commented on MSITE-395:
------------------------------

Can get site:site to work if each of the modules has the following.  

Parent

<properties>
    <site.version>2.0</site.version>
  </properties>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-site-plugin</artifactId>
        <version>${site.version}</version>
        <configuration>
          <locales>en</locales>
        </configuration>
      </plugin>
    </plugins>
  </build>


Modules
<build>
    <plugins>
      <plugin>
        <artifactId>maven-site-plugin</artifactId>
        <version>${site.version}</version>
        <configuration>
          <locales>en</locales>
          <outputDirectory>${project.parent.reporting.outputDirectory}/${name}</outputDirectory>
        </configuration>
      </plugin>
    </plugins>
  </build>

> Maven site multi module url problem
> -----------------------------------
>
>                 Key: MSITE-395
>                 URL: http://jira.codehaus.org/browse/MSITE-395
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: multi module
>    Affects Versions: 2.0
>            Reporter: valsho
>            Priority: Blocker
>
> The generated maven (2.0.10) site for a multi module project is different on windows and linux.
> The difference is the relative url for the modules. 
> --------------------------------------------------
> Here's the project structure :
> myProject/
>    trunk/
>       pom.xml
>       module1/
>          pom.xml
>          src/
>       module2/
>          pom.xml
>          src/
> --------------------------------------------------
> Here's myProject/trunk/pom.xml definition :
>   <groupId>com.myProject</groupId>
>   <artifactId>modulepom</artifactId>
>   <packaging>pom</packaging>
>   <name>POM myProject</name>
>   <version>1.0-SNAPSHOT</version>
>   
>  <modules>
>   <module>module1</module>
>   <module>module2</module>
>  </modules>
> <distributionManagement>
> 	<site>
> 		<id>site</id>
> 		<name>Maven site</name>
> 		<url>file://</url>
> 	</site>
> </distributionManagement>
> <build>
> <plugin>
> 	<groupId>org.apache.maven.plugins</groupId>
> 	<artifactId>maven-site-plugin</artifactId>
> 	<version>2.0</version>
> </plugin>
> </build>
> --------------------------------------------------
> On module1 and module2 pom, I didn't declare any <distributionManagement> information.
> I've "only" declared the parent
> 	  <parent>
> 	 	<groupId>com.myProject</groupId>
> 	 	<artifactId>modulepom</artifactId>
> 	 	<version>1.0-SNAPSHOT</version>
> 	 </parent>
> 	  
> 	  <groupId>com.myProject</groupId>
> 	  <artifactId>module1</artifactId>
> 	  <packaging>jar</packaging>
> 	  <version>1.0-SNAPSHOT</version>
> 	  <name>module1 name</name>
> --------------------------------------------------
> Here are the index.html files generated on windows and linux in myProject/trunk/target/staging/localhost/ after launching mvn site:stage in directory myProject/trunk/ 
> --> Site deployed on Windows which is correct
>      ....
>     <h5>Modules</h5><ul>
>     <li class="none">
>         <a href="module1/index.html">module1 name</a>
>     </li>
>               
>     <li class="none">
>         <a href="module2/index.html">module2 name</a>
>     </li>
>      ...
> --> Site deployed on Linux which isn't correct
>       ...
>       <h5>Modules</h5><ul>          
>       <li class="none">
>           <a href="../../tmp/testProject/myProject/trunk/../localhost">module1 name</a>
>       </li>
>            
>       <li class="none">
>           <a href="../../tmp/testProject/myProject/trunk/../localhost">module2 name</a>
>       </li>
>        ...
> where /tmp/testProject/ is the absolute path where is stored myProject/ on linux
> --------------------------------------------------
> Any idea ?
> Maybe i should use something different in <distributionManagement> than <url>file://</url>
> Thanks for your help

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