> The suggested work around seems a reasonable short term solution but
> forever maintaining 2 directories per workspace seems an awkward long
> term solution. (I routinely switch between several workspaces in my day
> and maintain at least one workspace on two other machines)
The workaround is better than you think. You are not maintaining 2
directories. You do a checkout from SVN so that you have a single WC
folder with all of your project. When you then do the Eclipse project
import, it just points your workspace at that other folder. This is
documented in our help under the Tips and Tricks section (at least I think
that is where it is).
You also mentioned atomic commits, however this does not effect atomic
commits within Subclipse one way or the other. The only way that Subclipse
does atomic commits across projects is to use JavaSVN. And it will do the
atomic commits even without a "parent WC" structure. IOW, you can just do
a normal checkout within Subclipse and still do atomic commits. Of course
with the other structure, you can always use the SVN command line or
another client to do an atomic commit.
> Having read this, the error message and the faq entry I think I have a
> handle on what's happening. I can believe these null references would
> cause a problem but why are they a non-issue in the workspace is wc case?
I think it is just because we do not need a reference to the .metadata
folder. Something about having a structure like this causes it to be sent
through some of the API's.
I setup a WC like this last Friday and fixed whatever problems I could
find, including skipping sending the message in this scenario. I
backported it for the 1.0 release.
Feel free to submit a patch for a better message, it is sent from the
SVNWorkspaceRoot class in the core plugin. As you will see when you get in
there, at the place the error occurs there is not a lot of context to work
with to provide more detail in the message. I am sure the wording could
always be explained. I intentionally wanted the message to be long and
verbose because I added code to only send it one time per session and I did
not want users to ignore it.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Apr 2 14:37:08 2006