You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jens breitenstein (JIRA)" <ji...@codehaus.org> on 2008/04/23 16:15:55 UTC
[jira] Created: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
wrong SVN directory path created when using cascaded pom modules(?)
-------------------------------------------------------------------
Key: MCHANGELOG-84
URL: http://jira.codehaus.org/browse/MCHANGELOG-84
Project: Maven 2.x Changelog Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: java 1.5.0_13 / mac os x / maven 2.0.7
Reporter: jens breitenstein
When executing "site" the plugin accesses a wrong svn path (see log below).
the pom look similar to this (well, I simplified it a bit :-)
root.pom
------------
<project>
...
<modules>
...
<module>configuration</module>
...
</modules>
....
</project>
pom (in directory configuration)
------------------------------------------
<project>
<parent> ... root.pom ... </parent>
....
<modelVersion>4.0.0</modelVersion>
<groupId>my.group.configuration</groupId>
<artifactId>PREFIX-configuration</artifactId>
<packaging>jar</packaging>
....
</project>
directory layout:
<directory trunk>
`---- root-pom
`---- <directory configuration>
`---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
[INFO] Generating "Change Log" report.
[INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
[INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
[INFO] Working directory: /****/trunk/configuration
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
"PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like "https://***/svn/***/trunk/configuration" and not "https://***/svn/***/trunk/PREFIX-configuration".
In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGELOG-84:
--------------------------------------
Description:
When executing "site" the plugin accesses a wrong svn path (see log below).
the pom look similar to this (well, I simplified it a bit :-)
root.pom
------------
{code:xml}
<project>
...
<modules>
...
<module>configuration</module>
...
</modules>
....
</project>
{code}
pom (in directory configuration)
------------------------------------------
{code:xml}
<project>
<parent> ... root.pom ... </parent>
....
<modelVersion>4.0.0</modelVersion>
<groupId>my.group.configuration</groupId>
<artifactId>PREFIX-configuration</artifactId>
<packaging>jar</packaging>
....
</project>
{code}
directory layout:
{noformat}
<directory trunk>
`---- root-pom
`---- <directory configuration>
`---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
{noformat}
[INFO] Generating "Change Log" report.
[INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
[INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
[INFO] Working directory: /****/trunk/configuration
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
"PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
was:
When executing "site" the plugin accesses a wrong svn path (see log below).
the pom look similar to this (well, I simplified it a bit :-)
root.pom
------------
<project>
...
<modules>
...
<module>configuration</module>
...
</modules>
....
</project>
pom (in directory configuration)
------------------------------------------
<project>
<parent> ... root.pom ... </parent>
....
<modelVersion>4.0.0</modelVersion>
<groupId>my.group.configuration</groupId>
<artifactId>PREFIX-configuration</artifactId>
<packaging>jar</packaging>
....
</project>
directory layout:
<directory trunk>
`---- root-pom
`---- <directory configuration>
`---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
[INFO] Generating "Change Log" report.
[INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
[INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
[INFO] Working directory: /****/trunk/configuration
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
"PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like "https://***/svn/***/trunk/configuration" and not "https://***/svn/***/trunk/PREFIX-configuration".
In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133239#action_133239 ]
Dennis Lundberg commented on MCHANGELOG-84:
-------------------------------------------
When a child module doesn't specify an <scm> element, it will inherit one from the parent. During this inheritance the artifactId of the child will be appended to the <scm> URLs from the parent. In your case the inherited <scm> URLs for the child project will look like this
{code:xml}
<scm>
<connection>scm:svn:https://user:password@myserver.de/svn/***/trunk/PREFIX-configuration</connection>
<url>scm:svn:https://user:password@myserver.de/svn/***/trunk/PREFIX-configuration</url>
<developerConnection>scm:svn:https://user:password@myserver.de/svn/***/trunk/PREFIX-configuration</developerConnection>
</scm>
{code}
This is the expected behavior.
If you want to use other URLs you will need to specify them explicitly in the POM of your child project, like this:
{code:xml}
<scm>
<connection>scm:svn:https://user:password@myserver.de/svn/***/trunk/configuration</connection>
<url>scm:svn:https://user:password@myserver.de/svn/***/trunk/configuration</url>
<developerConnection>scm:svn:https://user:password@myserver.de/svn/***/trunk/configuration</developerConnection>
</scm>
{code}
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133254#action_133254 ]
Dennis Lundberg commented on MCHANGELOG-84:
-------------------------------------------
OK, I'll try again, this time with *feeling*:
The path to a child directory, when using the aggregator, is *not* used when constructing the SCM URLs. Only the artifactId is used.
If you want to examine what your POM looks like you can run this command:
mvn help:effective-pom
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGELOG-84.
-------------------------------------
Resolution: Not A Bug
I added an entry on the FAQ page about SCM URL inheritance.
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Rintcius Blok (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133250#action_133250 ]
Rintcius Blok commented on MCHANGELOG-84:
-----------------------------------------
I expected the SVN path to be in line with the one that is by default used in the release plugin (if I don't specify a scm element in the child project). And the release plugin seems to use the aggregate (though I don't the exact algorithm how it creates the url).
And to me it makes sense that the SVN path uses the aggregator since these are typically tagged together (for the same reason that you mentioned that they are built simultaneously). The parent on the other hand is just providing defaults at definition time. In my case, it is the parent of completely unrelated projects for which it doesn't make sense to tag them together (or any other runtime mvn task)
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "jens breitenstein (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131887#action_131887 ]
jens breitenstein commented on MCHANGELOG-84:
---------------------------------------------
sorry I forgot that leading spaces are lost.... the "sub-module-pom" in my sketched "directory layout" is not indented correctly (imagine 4-6 spaces on the left, than the layout is fine ;-) "sub-module-pom" is contained within the sub-directory "configuration".
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> pom (in directory configuration)
> ------------------------------------------
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> directory layout:
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like "https://***/svn/***/trunk/configuration" and not "https://***/svn/***/trunk/PREFIX-configuration".
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Rintcius Blok (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133311#action_133311 ]
Rintcius Blok commented on MCHANGELOG-84:
-----------------------------------------
Ah ok that makes sense. The effective-pom showed that the SCM URLs were different than I thought they were, when I refer to a *released* version of the parent pom. In that case the SCM url of the parent pom is changed to a tags/parent-pom-<version>. I assumed that what was specified under the SCM element in the parent just served as a template, but in case of a release it is changed to the actual url.
Maybe something can be added to the FAQ about checking the SCM element in the effective-pom since that is quite helpful to get more insight in more complex situations. And it makes perfectly clear when the source of the unexpected behavior is outside the scope of the changelog plugin.
Anyway, thanks for your explanation Dennis!
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133248#action_133248 ]
Dennis Lundberg commented on MCHANGELOG-84:
-------------------------------------------
A project doesn't inherit from an aggregator project - it inherits from a parent project. The aggregator merely triggers the build of a bunch of projects simultaneously.
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Rintcius Blok (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133244#action_133244 ]
Rintcius Blok commented on MCHANGELOG-84:
-----------------------------------------
I believe I have the same problem. What goes wrong in my case is that the url is based on the *parent* but it should be based on the *aggregator* (see http://maven.apache.org/pom.html#Inheritance_v )
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132746#action_132746 ]
Dennis Lundberg commented on MCHANGELOG-84:
-------------------------------------------
Please share with us the <scm> configuration from your parent and configuration POMs.
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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: (MCHANGELOG-84) wrong SVN directory path created
when using cascaded pom modules(?)
Posted by "jens breitenstein (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133030#action_133030 ]
jens breitenstein commented on MCHANGELOG-84:
---------------------------------------------
Hello Denis.
See below the scm configuration. this configuration is only contained once in the root pom which also defines the modules (thanks for the beautiful formatting)
{code:xml}
<scm>
<connection>scm:svn:https://user:password@myserver.de/svn/***/trunk</connection>
<url>scm:svn:https://user:password@myserver.de/svn/***/trunk</url>
<developerConnection>scm:svn:https://user:password@myserver.de/svn/***/trunk</developerConnection>
</scm>
{code}
> wrong SVN directory path created when using cascaded pom modules(?)
> -------------------------------------------------------------------
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
> Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
> ------------
> {code:xml}
> <project>
> ...
> <modules>
> ...
> <module>configuration</module>
> ...
> </modules>
> ....
> </project>
> {code}
> pom (in directory configuration)
> ------------------------------------------
> {code:xml}
> <project>
> <parent> ... root.pom ... </parent>
> ....
> <modelVersion>4.0.0</modelVersion>
> <groupId>my.group.configuration</groupId>
> <artifactId>PREFIX-configuration</artifactId>
> <packaging>jar</packaging>
> ....
> </project>
> {code}
> directory layout:
> {noformat}
> <directory trunk>
> `---- root-pom
> `---- <directory configuration>
> `---- sub-module-pom this file defines the artifact "PREFIX-configuration.jar"
> {noformat}
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to: /******/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username **** --password ***** --non-interactive log -v -r "{2008-03-24 13:32:56 +0000}:{2008-04-24 13:32:56 +0000}" https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: /****/trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461/****/trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a directory. The root pom access this child pom via the module element "configuration" which is identical to the directory in the file system and the svn repository. So correctly the svn command should look like {noformat}"https://***/svn/***/trunk/configuration"{noformat} and not {noformat}"https://***/svn/***/trunk/PREFIX-configuration"{noformat}.
> In case I understand the error message correctly the plugin tries to read a directory which is named like the artifact-id which is wrong here?
--
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