[
http://jira.codehaus.org/browse/MRELEASE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87714
]
Dan Tran commented on MRELEASE-199:
-----------------------------------
I have never heard a successfull release with project structure using relative
path. I think there are JIRA for this already.
So here are the rules to get a successful release:
1. Using a tree structure project. It means your top project is your root
pom.
2. AtifactId and directory name must match, other wise you need to configure
you SCM element for each project which
is very error prone.
Take a look continuum and maven maven-scm, etc
> Getting SVN error "not working copy" during release:prepare
> -----------------------------------------------------------
>
> Key: MRELEASE-199
> URL: http://jira.codehaus.org/browse/MRELEASE-199
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> 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 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
