[
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
