Hi all,
does the release plugin expect any special organisation of code in svn? i have mutliproject which looks like this:

-tagging (note, this parent folder is not under version control)
|- root
|-.svn
|-pom.xml (parent pom)
|- child1
|-.svn
|-pom.xml
|- child2
|-.svn
|-pom.xml
|- child3
|-.svn
|-pom.xml

with an subversion structure like this:

|-tagging
|-root
 |-branches
 |-tags
 |-trunk (<-- this is checked out into folder 'tagging')
  |- pom.xml
|-child1
 |-branches
 |-tags
 |-trunk (<-- this is checked out into folder 'tagging')
  |- pom.xml
|-child2
 |-branches
 |-tags
 |-trunk (<-- this is checked out into folder 'tagging')
  |- pom.xml
|-child3
 |-branches
 |-tags
 |-trunk (<-- this is checked out into folder 'tagging')
  |- pom.xml

when i now do a mvn release:prepare I get following exeception (this is because the parent folder 'tagging' is not under version control)

INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /home/slartibartfast/Development/workspaces/spring/tagging/root && svn --non-interactive commit --file /tmp/maven-scm-1136921401.commit --targets /tmp/maven-scm-8710897044971377748-targets [INFO] Working directory: /home/slartibartfast/Development/workspaces/spring/tagging/root [INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/home/slartibartfast/Development/workspaces/spring/tagging' is not a working copy svn: Can't open file '/home/slartibartfast/Development/workspaces/spring/tagging/.svn/entries': No such file or directory

So my questions is: can I make this somehow work with my current project/svn layout or would I have to make changes to it? Any Ideas? Thanks.
Regards,
Gerhard

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to