You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eric Miles (JIRA)" <ji...@codehaus.org> on 2009/12/21 21:05:58 UTC
[jira] Issue Comment Edited: (MRELEASE-261) release:prepare shouls
support flat directory multimodule projects
[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203270#action_203270 ]
Eric Miles edited comment on MRELEASE-261 at 12/21/09 2:04 PM:
---------------------------------------------------------------
I'm not 100% sure this is fixed. I setup a project to use the beta-10-SNAPSHOT plugin and it is still not working, I'm getting the following error while trying to prepare the release:
{code}
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /Users/emiles/Projects/release-workspace/release-parent && svn --non-interactive commit --file /var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-1253932520.commit --targets /var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-4376558781490229966-targets
[INFO] Working directory: /Users/emiles/Projects/release-workspace/release-parent
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{code}
I have confirmed that I am using the beta 10 release as well as I have confirmed the beta 10 release in Apache snapshots contained the v3.patch identified in one of the previous comments. I'm attaching my sample project, maven-release-issue.tar.gz. I'm hoping this can be used as a test case and/or someone can tell me if I've set the project up incorrectly.
This work is being performed in a Mac OS X environment with JDK 1.5 and SVN 1.6.6.
An update...I have completely removed the release plugin and am only using the svn binary on my box. I still get the same issue, issuing a similar command
{code}
emiles-macbook:~ emiles$ svn --non-interactive commit --file /tmp/svn-msg --targets /tmp/targets
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{code}
Here's a cat of svn-msg:
{code}
emiles-macbook:~ emiles$ cat /tmp/svn-msg
[maven-release-plugin] prepare release release-parent-0.0.1emiles-macbook:~ emiles$
{code}
And a cat of targets:
{code}
emiles$ cat /tmp/targets
/Users/emiles/Projects/release-workspace/release-parent/pom.xml
/Users/emiles/Projects/release-workspace/release-module1/pom.xml
/Users/emiles/Projects/release-workspace/release-module2/pom.xml
{code}
So that this point, I'm beginning to wonder if it's the svn binary causing an issue, at this point we have completely circumvented the release plugin. Or maybe it's the way the release plugin is attempting to use SVN?
was (Author: bigehokie):
I'm not 100% sure this is fixed. I setup a project to use the beta-10-SNAPSHOT plugin and it is still not working, I'm getting the following error while trying to prepare the release:
{code}
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /Users/emiles/Projects/release-workspace/release-parent && svn --non-interactive commit --file /var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-1253932520.commit --targets /var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-4376558781490229966-targets
[INFO] Working directory: /Users/emiles/Projects/release-workspace/release-parent
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{code}
I have confirmed that I am using the beta 10 release as well as I have confirmed the beta 10 release in Apache snapshots contained the v3.patch identified in one of the previous comments. I'm attaching my sample project, maven-release-issue.tar.gz. I'm hoping this can be used as a test case and/or someone can tell me if I've set the project up incorrectly.
This work is being performed in a Mac OS X environment with JDK 1.5 and SVN 1.6.6.
> release:prepare shouls support flat directory multimodule projects
> ------------------------------------------------------------------
>
> Key: MRELEASE-261
> URL: http://jira.codehaus.org/browse/MRELEASE-261
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Environment: linux / maven2 / svn
> Reporter: paul.whelan@gmail.com
> Assignee: Maria Odea Ching
> Fix For: 2.0-beta-10
>
> Attachments: flatProject.main.patch, flatProject.test.patch, maven-release-issue.tar.gz, MRELEASE-261-with-its-v3.patch, MRELEASE-261-with-its.patch, MRELEASE-261.patch, PrepareReleaseMojo.patch
>
>
> What I mean by flat file structure firstly.
> parent/pom.xml
> module1/pom.xml
> module2/pom.xml
> .
> .
> .
> module15/pom.xml
> the parent references the modules like so
> <modules>
> <module>../module1</module>
> <module>../module2</module>
> .
> .
> .
> <module>../module15</module>
> </modules>
> When i release:prepare only the parent project is tagged the modules projects versions are incremented etc but the modules are not tagged in svn.
> I use this structure as i use eclipse as my IDE.
> I would love to see a fix for the issue marked as closed here http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand each submodule of the projects but it would be so nice to have the release plugin do this for me.
> forgive my english.
--
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