"Ball, Rick" <Rick_Ball@bose.com> wrote on 10/10/2006 09:57:41 AM:
> I'm trying to get started using Subclipse, and I'm having trouble
'sharing'
> a new project. I think I'm following the instructions in the help file,
but
> for some reason it's not working.
> I have Subversion 1.4.0 and TortoiseSVN 1.4.0.7501 installed, along with
> Eclipse 3.2, CDT 3.1.0, and Subclipse 1.1.7 (and a Green Hills plug-in,
> which I don't think should be causing a problem).
> I created a brand new repository on a network share (FSFS), using
> TortoiseSVN -> 'Create repository here?'. Then, I right-clicked on my
> project in Eclipse and selected 'Team -> Share Project'. In the wizard,
I
> selected SVN, then my repository location, and then clicked the radio
button
> to 'Use specified folder name'. I then used the browse button to open
the
> repos, right-clicked to select 'New Remote Folder', and entered the
project
> name ('target'). Then, back in the folder name, I changed 'target/New
> folder' to 'target/trunk', and clicked 'Finish'. I got the expected
> messages for a mkdir of the 'trunk' folder, and the checkout, and then
got a
> pop-up that said 'No files were changed or added since the last commit'
(not
> sure if that's expected or not). After a few seconds, whether or not I
> closed the pop-up, I get another pop-up with the following error:
> 'An internal error occurred during: "Updating Change Sets for
> SVNStatusSubscriber'.
> I found a mention of this error in the mailing list, but the belief
there
> seems to be that it's a bug in JavaSVN, and I'm using JavaHL (at least,
> that's what my Preferences window says).
> I don't know how to get a stack trace (maybe the 'Details >>' button on
the
> error dialog? But that button is grayed-out...)
I would think this error could be ignored and you would be OK. You do not
really state what trouble you are in after you get this error. It sounds
like it would share the project.
The error sounds like you have the Synch view open with an active Synch
and some error is happening in refreshing that information. You could try
closing all synchronizations.
You can open the view PDE Runtime -> Error Log to see any stack traces, or
open the file workspace/.metadata/.log.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Oct 10 16:01:48 2006