[
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
