I guess that at one time during release:prepare the clean phase is
executed, which causes the target directory to be deleted. (Including
your working copy information i.e. .svn directory) In my experience it
is better to exclude the target directory from version control, as it is
a working copy local directory. So remove your target directory and put
a svn:ignore property on the directory in which the target directory is
created. Also files like .classpath and .project (for eclipse users) are
candidates for exclusion because they are often workspace specific.
Root <- svn:ignore here
-pom.xml
-module1 <- svn:ignore here
-pom.xml
-src
-main
-java
-test
-java
-target
-module2 <- svn:ignore here
-pom.xml
-src
-main
-java
-test
-java
-target
-target
Hth,
Nick Stolwijk
ossi petz wrote:
hallooo
i am trying to get me thorugh the release steps using maven 2.0.5 and
subversion.
i have created several modules (pretty similar to the spring migration
example from the book) abd done a checkout.
within the directory of the parent pom i execute:
# mvn release:prepare
this fails with the error:
Command output:
svn: directory C:\eclipse-ws\release\project.server\target\.svn
containing working copy admin area is missing
that folder (.svn) was there on the initial checkout. but somehow it
seems to be deleted and recreated during the prepare steps??
furthermore (as this step fails) the pom.xml files of the modules in
the subversion repository have a changed version, the are no longer
snapshots!?
does anyone has a clue how to fix this?
thanks a lot
regards
op
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
