maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-199) Getting SVN error "not working copy" during release:prepare
Date Tue, 25 Nov 2014 20:49:51 GMT

     [ https://jira.codehaus.org/browse/MRELEASE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov closed MRELEASE-199.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.

> Getting SVN error "not working copy" during release:prepare
> -----------------------------------------------------------
>
>                 Key: MRELEASE-199
>                 URL: https://jira.codehaus.org/browse/MRELEASE-199
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-4, 2.0-beta-5
>         Environment: PC XP Pro
>            Reporter: Brian Ely
>            Priority: Critical
>         Attachments: testc.txt
>
>
> I've search around the web finding problems similar but not exactly like mine.  Hopefully
someone out there can help me.  I'm trying to build a tagged release and code versioning using
maven (2.0.4 & 2.0.5) with subversion (win32-1.4.2).  According to documentation, all
I would need to do is do the release:prepare dryrun first and the full prepare second using
the files from the dryrun.  This succeeds in a successful build but no tags.
> The next step, release:perform, complains of no tag release during checkout.
> I saw a bulletin board conversation indicating that a "release:clean" was required between
the dryrun and full prepare in order to get the tags.  This results in the error "not a working
copy" from SVN - see attachment (from the run of the full prepare with -e -X options).   Any
run of the release:perform results in the complaint that the tags does not exist.  The exact
commands are as follows:
> mvn -DdryRun=true release:prepare
> mvn release:clean
> mvn -e -X release:prepare
> It appears the "working copy" directory was not built out correctly (from the error log
in attachment):
> svn: 'C:\Builds\multipgm\Latest\src' is not a working copy
> svn: Can't open file 'C:\Builds\multipgm\Latest\src\.svn\entries': The system cannot
find the path specified.  
> I believe the path is not built out correctly and is missing paths between the src and
.svn.
> I appreciate any help here, since this is a showstopper and from what I can tell should
work according to Maven documentation.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message