[
https://issues.apache.org/jira/browse/MRELEASE-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720224#comment-15720224
]
Peter Rader edited comment on MRELEASE-970 at 12/4/16 4:37 PM:
---------------------------------------------------------------
The pain is every time, not only the first time. But we learn to live with that
pain every time so it is not a suprising anymore and we did not wonder anymore
and need no help anymore but still its pain every time. And after the first
pain we are going to be part of the majority, the painful majority. The pain is
dead, long lives the pain.
No, the trunk-url is not part of the tag-url but the trunk-url and the tag-url
have the same prefix: the real project's connection. Even if the tag url
contains relative parts like "/xxx/trunk/../tags/xxx-1.0" it does not explain
why without the "/trunk"-postfix in connection and developerConnection it finds
my "/xxx/tags/" directory.
Lets stop here, I accept that the bug will not be solved for compatibility
reasons.
was (Author: grim):
The pain is every time, not only the first time. But we learn to live with that
pain every time so it is not a suprising anymore and we did not wonder anymore
and need no help anymore but still its pain every time. And after the first
pain we are going to be part of the majority, the painful majority. The pain is
dead, long lives the pain.
No, the trunk-url is not part of the tag-url but the trunk-url and the tag-url
have the same prefix: the real project's connection. Even if the tag url
contains relative parts like "/xxx/trunk/../tags/xxx-1.0" it does not explain
why without the "/trunk"-postfix in connection and developerConnection it finds
my "/xxx/tags/" directory.
Lets stop here, i accept that the bug will not be solved for compatibility
reasons.
> Check that a pom.xml exists in the <scm><connection>-folder
> -----------------------------------------------------------
>
> Key: MRELEASE-970
> URL: https://issues.apache.org/jira/browse/MRELEASE-970
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.3.2, 2.5.3
> Environment: Linux64
> Reporter: Peter Rader
> Assignee: Robert Scholte
> Priority: Minor
> Attachments: bug-release-perform-maven.png,
> bug-release-perform-maven.txt
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> In releasing a new version having a wron scm-connection, a recursion in
> checkout occours.
> {noformat}
> [ERROR] svn: E155009: Failed to run the WC DB work queue associated with
> '/home/release/rel/trunk/target/checkout/tags/Vector-Publish-0.9.17/tags/Vector-Publish-0.9.16/tags/Vector-Publish-0.9.15/tags/Vector-Publish-0.9.12/tags/Vector-Publish-0.9.10/net.vectorpublish.desktop.vp/src/main/resources/iconset/FatCow_Icons32x32',
> work item 399473 (file-install 225
> tags/Vector-Publish-0.9.17/tags/Vector-Publish-0.9.16/tags/Vector-Publish-0.9.15/tags/Vector-Publish-0.9.12/tags/Vector-Publish-0.9.10/net.vectorpublish.desktop.vp/src/main/resources/iconset/FatCow_Icons32x32/user_robocop.png
> 1 0 1 1)
> [ERROR] svn: E000028: Can't create temporary file from template
> '/home/release/rel/trunk/target/checkout/.svn/tmp/svn-XXXXXX': No space left
> on device
> {noformat}
> Please note: "No space left on device" is not correct, it points to a
> too-long-directory-path. I have 30GB on svn-server and 1,6GB free on local.
> Could you add a check that a pom.xml exists in the <connection> url?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
