Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
3.0-beta-3
-
None
-
None
-
Windows XP SP3
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
Description
In my corporative pom:
<project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>mycompany</groupId>
<artifactId>corporative-pom</artifactId>
<version>1.0.0</version>
<packaging>pom</packaging>
I've configured the site url:
<distributionManagement>
<site>
<id>myserver</id>
<url>file://myserver/c$/Tomcat6.0/webapps</url>
<name>myserver</name>
</site>
</distributionManagement>
Than, in a multimodule project MULT, the subproject SUB needs to be deployed into c$/Tomcat6.0/webapps, so the url would be http://myserver/SUB/index.html
To do this I've configured the SUB pom in this way:
<project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>mycompany</groupId>
<artifactId>corporative-pom</artifactId>
<version>1.0.0</version>
<relativePath /> <!-- doesn't use the MULT pom, but uses the corporative-pom pom -->
</parent>
<artifactId>SUB</artifactId>
<version>1.0.0</version>
<packaging>jar</packaging>
<url>/${project.artifactId}</url> <!-- it should returns SUB -->
...
</project>
The goal site:deploy (Maven2 site plugin) on the SUB project correctly deploys into e new created http://myserver/SUB, but using Maven 3 the goal site:deploy (Maven3 site plugin) incorrectly deploys into e new created http://myserver/corporative-pom/SUB directory.
Such behaviour happens even if in SUB pom I've configured a <url>/aaaaaaaaaa</url>, or I've configured no <url> at all.
In my opinion it seems, in this case, that Maven3 site:deploy goal wrongly builds the url string.
Thanks,
Tarin