Mark,
If I import a project set, such that the new projects are created in the workspace folder, the SVN connection is created without trouble.
If I cerate the SVN working copy outside of Eclipse (which works fine), and then create a Java project from the existing code, the project is created, but is not connected to SVN and produces the error dialog I described.
If subsequently I try to connect the project to SVN, it tries to send the whole project to the repository, creating a whole new directory in the repository. So apparently it is not apparent to the SW that the directory contains all the requisite .svn information.
I'll be glad to do any experimentation that would be helpful to you. I will later try to reinstall and retry this.
- David
----- "Mark Phippard" <markphip_at_gmail.com> wrote:
> On Thu, Sep 3, 2009 at 8:50 PM, David Cok<cok_at_frontiernet.net> wrote:
> > I'm wondering (a) if anyone else has experienced this on Mac-Leopard
> with
> > the most recent versions of subversion and subclipse, and (b) if it
> is
> > considered a problem of reasonably high priority, [ or (c) if I've
> messed up
> > my installation somehow.] Recorded as issue #989.
>
> I just tested that it still works for me. I am on Snow Leopard and
> using the CollabNet Mac binaries (which includes the needed 64-bit
> version of JavaHL).
>
>
> > I have a subversion working copy (including project information)
> outside of
> > Eclipse and then attempt to
> > import the existing project. The project imports, but it does not
> recognize
> > that it is a SVN project - and
> > in fact produces an error dialog with this detail:
> > java.lang.NullPointerException
> > at
> >
> org.tigris.subversion.subclipse.core.resources.SVNWorkspaceRoot.setSharing(SVNWorkspaceRoot.java:1
> > 71)
>
> So this is weird. I just tried to look at what the NPE could be
> caused by and line 171 is not within that method. In fact it is just
> a variable declaration. This file has not changed since November of
> last year so I cannot figure out why your stack trace would not be
> right.
>
> I have to think my brain must not be functioning right yet as I just
> cannot see how the stack trace could give me the wrong line of code.
> So I will keep thinking about it.
>
> It seems like you ought to be able to checkout from within Eclipse
> and
> then have it connected.
>
> Also, if you restart Eclipse and the project is present, what happens
> if you do Team > Share?
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ------------------------------------------------------
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2391002
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe_at_subclipse.tigris.org].
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2391280
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-09-05 14:06:08 CEST