You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "valsho (JIRA)" <ji...@codehaus.org> on 2009/03/25 15:13:13 UTC
[jira] Created: (MSITE-395) Maven site multi module url problem
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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "Albert Kurucz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175631#action_175631 ]
Albert Kurucz commented on MSITE-395:
-------------------------------------
Hi Dennis,
If you are still in need of a test project, you can use mine:
svn checkout http://jtstand.googlecode.com/svn/trunk/jtstand
This is has 3 modules.
I have the same problem on Linux as above. (not tried it on Windows, because
Reverting back to maven-site-plugin:2.0-beta-5 fixes it for me too.)
> 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
[jira] Issue Comment Edited: (MSITE-395) Maven site multi module
url problem
Posted by "Albert Kurucz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175631#action_175631 ]
Albert Kurucz edited comment on MSITE-395 at 5/10/09 1:45 AM:
--------------------------------------------------------------
Hi Dennis,
If you are still in need of a test project, you can use mine:
svn checkout http://jtstand.googlecode.com/svn/trunk/jtstand
This has 3 modules.
I have the same problem on Linux as above.
Reverting back to maven-site-plugin:2.0-beta-5 fixes it for me too,
the menu links OK, but beta-5 does not site:stage correctly.
It does site:site when I ask site:stage.
No copies of the modules' sites in the parent's "staging".
So I need to boot to Windows :-(
was (Author: ali65):
Hi Dennis,
If you are still in need of a test project, you can use mine:
svn checkout http://jtstand.googlecode.com/svn/trunk/jtstand
This has 3 modules.
I have the same problem on Linux as above.
Reverting back to maven-site-plugin:2.0-beta-5 fixes it for me too,
the menu links OK, but beta-5 does not site:stage correctly.
It does site:site when I ask site:stage.
So I need to boot to Windows :-(
> 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
[jira] Issue Comment Edited: (MSITE-395) Maven site multi module
url problem
Posted by "Albert Kurucz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175631#action_175631 ]
Albert Kurucz edited comment on MSITE-395 at 5/10/09 1:21 AM:
--------------------------------------------------------------
Hi Dennis,
If you are still in need of a test project, you can use mine:
svn checkout http://jtstand.googlecode.com/svn/trunk/jtstand
This has 3 modules.
I have the same problem on Linux as above. (not tried it on Windows, because
Reverting back to maven-site-plugin:2.0-beta-5 fixes it for me too.)
was (Author: ali65):
Hi Dennis,
If you are still in need of a test project, you can use mine:
svn checkout http://jtstand.googlecode.com/svn/trunk/jtstand
This is has 3 modules.
I have the same problem on Linux as above. (not tried it on Windows, because
Reverting back to maven-site-plugin:2.0-beta-5 fixes it for me too.)
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "Florian Kolbe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177133#action_177133 ]
Florian Kolbe commented on MSITE-395:
-------------------------------------
I can confirm this bug, using:
Linux
mvn 2.0.9
maven-site-plugin 2.0
I also get URLs of the kind:
<a href="../../tmp/testProject/myProject/trunk/../localhost">module2 name</a>
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172258#action_172258 ]
Dennis Lundberg commented on MSITE-395:
---------------------------------------
Without a test project it is very difficult for us to do anything. Please add one to this issue so that we can try to reproduce your problem.
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "Lance Linder (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173125#action_173125 ]
Lance Linder commented on MSITE-395:
------------------------------------
Just ran into this same issue tonight.
Ubuntu 8.10
Maven 2.0.10 and 2.1.0
Maven Site Plugin 2.0
Command: mvn clean site-deploy
I am also getting this problem using the menu tag in the site.xml body.
One windows the relative href links in my menu item tags work fine but on linux they end up the same as described by Murry.
Reverting back to maven-site-plugin:2.0-beta-5 fixes it for me too.
I will try and cook up a sample project soon but honestly my project is just a basic standard maven module project with very basic site.xml config.
> 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
[jira] Issue Comment Edited: (MSITE-395) Maven site multi module
url problem
Posted by "murray (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171778#action_171778 ]
murray edited comment on MSITE-395 at 4/2/09 4:40 AM:
------------------------------------------------------
2.0-beta-5
has correct links but no content for modules
was (Author: onekilo79):
maven-site-plugin
2.0-beta-5 works fine. No need for <distributionManagement>
> 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
[jira] Closed: (MSITE-395) Maven site multi module url problem
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl closed MSITE-395.
-------------------------------
Assignee: Lukas Theussl
Resolution: Fixed
Seems fixed with MSITE-404, please test.
> 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
> Assignee: Lukas Theussl
> Priority: Blocker
> Fix For: 2.1
>
> Attachments: genesis-2.0-SNAPSHOT-source-release.tar.gz, genesis-2.0-SNAPSHOT-source-release.tar.gz
>
>
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "murray (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171713#action_171713 ]
murray commented on MSITE-395:
------------------------------
happens with or without the <distributionManagement>
on both site and site:stage
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "murray (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Issue Comment Edited: (MSITE-395) Maven site multi module
url problem
Posted by "Albert Kurucz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175631#action_175631 ]
Albert Kurucz edited comment on MSITE-395 at 5/10/09 1:43 AM:
--------------------------------------------------------------
Hi Dennis,
If you are still in need of a test project, you can use mine:
svn checkout http://jtstand.googlecode.com/svn/trunk/jtstand
This has 3 modules.
I have the same problem on Linux as above.
Reverting back to maven-site-plugin:2.0-beta-5 fixes it for me too,
the menu links OK, but beta-5 does not site:stage correctly.
It does site:site when I ask site:stage.
So I need to boot to Windows :-(
was (Author: ali65):
Hi Dennis,
If you are still in need of a test project, you can use mine:
svn checkout http://jtstand.googlecode.com/svn/trunk/jtstand
This has 3 modules.
I have the same problem on Linux as above. (not tried it on Windows, because
Reverting back to maven-site-plugin:2.0-beta-5 fixes it for me too.)
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "murray (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171712#action_171712 ]
murray commented on MSITE-395:
------------------------------
Url problem happens on os x and in red hat linux . The relative paths are added without being asked for. it does work on windows xp.
Jdk
1.5.0_16
maven
2.1,2.0.9
maven-site-plugin
2.0-beta-6, 2.0.-beta7, & 2.0
> 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
[jira] Updated: (MSITE-395) Maven site multi module url problem
Posted by "David Jencks (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated MSITE-395:
-------------------------------
Attachment: genesis-2.0-SNAPSHOT-source-release.tar.gz
A cleaner project that still shows the same problem.
It appears to be possible to avoid using the site:stage goal and hopefully get a testable site by using a property for the site location:
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<siteId>genesis</siteId>
<site.deploy.url>scp://people.apache.org:/www/geronimo.apache.org</site.deploy.url>
</properties>
<distributionManagement>
<site>
<id>apache-website</id>
<url>${site.deploy.url}/maven/${siteId}/${version}</url>
</site>
</distributionManagement>
and running
mvn site site:deploy -Dsite.deploy.url=file:///Users/david/tmp/staging
> 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
> Attachments: genesis-2.0-SNAPSHOT-source-release.tar.gz, genesis-2.0-SNAPSHOT-source-release.tar.gz
>
>
> 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
[jira] Updated: (MSITE-395) Maven site multi module url problem
Posted by "David Jencks (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated MSITE-395:
-------------------------------
Attachment: genesis-2.0-SNAPSHOT-source-release.tar.gz
Another really simple example showing the problem. This is an apache project so you can use it in an integration test. It's
https://svn.apache.org/repos/asf/geronimo/genesis/trunk
rev 782541
A typical link looks like
<li class="none">
<a href="../../Users/david/geronimo/svn/geronimo/genesis/trunk/../../../../../../people.apache.org/www/geronimo.apache.org/maven/genesis/2.0-SNAPSHOT">Genesis Maven Plugin</a>
</li>
I ran
mvn site site:stage -DstagingDirectory=/Users/david/tmp/staging
The project is checked out locally to
/Users/david/geronimo/svn/geronimo/genesis/trunk
I'm on os x currently using java 1.6, maven 2.0.10, site plugin 2.0
> 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
> Attachments: genesis-2.0-SNAPSHOT-source-release.tar.gz
>
>
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "murray (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171778#action_171778 ]
murray commented on MSITE-395:
------------------------------
maven-site-plugin
2.0-beta-5 works fine. No need for <distributionManagement>
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "Jason Smith (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182332#action_182332 ]
Jason Smith commented on MSITE-395:
-----------------------------------
See MSITE-409 comments.
> 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
> Attachments: genesis-2.0-SNAPSHOT-source-release.tar.gz, genesis-2.0-SNAPSHOT-source-release.tar.gz
>
>
> 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
[jira] Commented: (MSITE-395) Maven site multi module url problem
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170990#action_170990 ]
Dennis Lundberg commented on MSITE-395:
---------------------------------------
file:// is not a valid URL, so I'd start by fixing that. Staging uses the value of the distributionManagement URL, so it'd better be correct.
You talk about both stage and deploy of the site. Which is it, stage or deploy? Those are different goals of the Site Plugin.
What kind of Linux are you running?
Can you please package up this into a test project and attach that as a zip file to this issue. That way we can use it to try to reproduce your problem.
> 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