I am having a problem using Tortoise SVN (or maybe subversion) with WSAD
5.1.2
My source files are setup as follows (which I believe is standard):
/myproject
/JavaSource
/com
/mypackage
/WebContent
/jsps
/WEB-INF
/classes
/mypackage
/lib
/config
The JavaSource gets compiled by WSAD under WEB-INF/classes.
Something then creates some (it doesn't seem like all) .svn files in the
WEB-INF/classes/... directories.
This causes Subversion/Tortoise to think that they are being versioned and
is mapping them to the original JavaSource directory. They then show up in
the commit dialog.
I have tried having Tortoise ignore this directory and got lots of errors.
The WEB-INF and classes file have a conflicted overlay (yellow triangle
with !).
I tried to "Update" WEB-INF and I get the message that it is locked and I
should run the Cleanup command.
I tried to "Cleanup" WEB-INF and I get the message "Subversion reported an
error doing a cleanup! ....\WEB-INF\classes is not a working directory."
I tried to "Commit" WEB-INF and the WEB-INF folder is "modified" and
classes folder is listed as "obstructed". Double clicking on WEB-INF shows
the difference screen with "svn:ignore : Working base" on the left and
"svn:ignore : Working Copy" on the right and has a + next to classes on
the right hand side.
It feels like WSAD is copying the .svn directories during a build. Though
it could be TortoiseSVN. It seems unlikely that it is Subversion itself.
Are there any recommendations for how best to use TortoiseSVN with WSAD?
Or am I better off using the unsupported Subclipse plug-in for Eclipse 2?
I am using Subversion the following versions:
TortoiseSVN 1.3.1, Build 5521 - 32 Bit
Subversion 1.3.0,
apr 0.9.7
apr-iconv 0.9.7
apr-utils 0.9.7
berkeley db 4.3.28
neon 0.25.4
OpenSSL 0.9.8a 11 Oct 2005
zlib 1.2.3
Thanks
Steve Martin
Steve Martin
Hewitt Associates LLC - TOC Technology
Email: ssmartin@hewitt.com
Phone: +847/771-5276
Fax: +847/295-0659
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Received on Thu Feb 2 08:17:09 2006