maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MRELEASE-970) Check that a pom.xml exists in the <scm><connection>-folder
Date Sun, 04 Dec 2016 16:05:58 GMT


Robert Scholte commented on MRELEASE-970:

The SCM section is first of all information, e.g. to be displayed on
and when downloaded thee jar from the repository you have a reference to the location with
the sources.

Only during the release process you specify the next tag and the maven-release-plugin will
update the SCM information. 
There is actually only a translation to the tag-location, the original (trunk) location is
never used/touched. It's value is only restored with the final SCM step. Hence, it doesn't
make sense to me to check it.

Be aware that Maven needs a mechanism which will work for all SCMs and right now it does.
The maven-release-plugin has enough options to adjust the calculation of the tag-location,
but the current default seems to work for the majority.

If you are aware of the plans of introducing the concept of build-pom and distribution-pom,
I'd like to investigate if we can remove scm from the build-pom and generate it for the distribution-pom.
For svn you can do {{svn info .}} to get that kind of information.

Another issue is documentation. It is clear to me that you either haven't read the maven-release-plugin
documentation or that we haven't been clear enough how to setup the scm.connection.
Also, once anyone has done a successful release with the maven-release-plugin, nobody looks
to the SCM anymore, it just works. If there's some pain, it's often the first attempt.

> Check that a pom.xml exists in the <scm><connection>-folder
> -----------------------------------------------------------
>                 Key: MRELEASE-970
>                 URL:
>             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

View raw message