"Glenn R. Golden" <ggolden@umich.edu> wrote on 03/21/2006 09:34:42 PM:
> We have a project (www.sakaiproject.org) that is switching over to
> heavy use of svn:externals. We have a root svn area that uses svn:
> externals settings to collect a number of Eclipse projects together.
>
> You can check it out with this command:
>
> svn co https://source.sakaiproject.org/svn/sakai/branches/sakai-2.2
>
> The checkout creates a "sakai-2.2" directory, and in there are the
> projects we want to import into Eclipse. Each of these projects has
> Eclipse .classpath and .project files checked in.
>
> I am having trouble getting these checked out modules to work with
> Subclipse in Eclipse
>
> Using import, or adding each one as a separate project into Eclipse,
> I get the following error related to the project's SVN information:
>
> An internal error occurred during: "Auto-sharing imported
subversionprojects".
> java.lang.NullPointerException
>
> A screen shot of the multi-project import is attached.
>
> The projects are in Eclipse work ok for Eclipse, but they do not
> have their SVN connection.
>
> Feel free to try this with the above SVN address.
>
> I wonder if I'm doing something wrong, if there's any way to make
> this work with this version, or if this is a bug or missing feature
> in Subclipse.
I just tried this and it worked fine. I am on Windows, but do not think
that should matter. Also, I did not have the command line available, so
this is what I did:
1) Create connection to URL you gave above in Subclipse.
2) Checkout project as Simple Project to a folder outside my workspace.
3) Deleted project in Eclipse, without deleting contents.
4) Deleted the .project file that was created by step 2.
5) File -> Import -> Existing Projects into Workspace.
6) Selected folder from step 2. It shows me all 5 projects.
7) Import successfully auto-shared all 5 projects. No error in console.
Ops like Show History work.
What version of the svn command line did you use to checkout the projects?
If it was not 1.3, maybe try it again using 1.3, or try my technique. I
know that 1.3 stores the repository root URL in the WC and earlier
versions did not. Auto-share uses that info if it is available, so maybe
if you are importing an svn:externals from a pre 1.3 WC you can get this
error?
That is my best guess.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Wed Mar 22 05:04:21 2006