[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Problem: Javahl interface is not available. Check your environment.

From: Jan Ploski <Jan.Ploski_at_offis.de>
Date: 2005-04-22 11:39:55 CEST

Jan Ploski <Jan.Ploski@offis.de> schrieb am 04/12/2005 01:31:00 PM:

> "Alexander Kitaev" <alex@tmate.org> schrieb am 04/12/2005 01:06:06 PM:
>
> > Hello Jan,
> >
> > What version of JavaSVN did you use?
>
> 0.8.7.2, installed via the update site today.
>
> > Were ".svn" directories created after checkout?
>
> Yes, the ".svn" directory (with some content) is present in the checked
> out
> project. However:
>
> 1. When I switch to Java perspective, the project does not seem to have
> any
> content - I have to Refresh it manually to see the downloaded files.
> 2. In the Error Log, the following message appears:
> "Project {0} does not contain SVN folder meta-information."
> 3. Next to the project name there are [] brackets with no repository
> location inside.
> 4. All contained files appear with the question mark decoration.
> 5. Trying "Add to Version Control" on a file will cause the error
message
> "The SVN synchronization information for {0} has become corrupt
> or does not exist."

Today, while trying to reproduce this problem in a debugged runtime
workbench, I got rid of it. Unfortunately, I cannot really explain how :-/

Here are some steps that might have helped:
1. I noticed a strange directory
"org.tigris.subversion.subclipse.core_0.9.30.1"
   (besides of the expected "org.tigris.subversion.subclipse.core_0.9.30")
under
   $ECLIPSE_HOME/plugins and deleted it.
2. I had intermittent (unrelated) problems with OutOfMemoryErrors,
   and at one time Eclipse would not start up. To fix it, I removed
   the file $WORKSPACE/.metadata/.registry
3. Reinstalled both Subclipse (0.9.30 now) and JavaSVN (0.8.8.1 now).
   I don't think it mattered because I could experience my problem during
   a period after the upgrade.

Anyway, Subclipse works as expected now. I think it would be a good idea
to place some assertions into the code to prepare for diagnosing the above
described problem when it strikes someone else.

Thank you for contributing to this thread.

Best regards -
Jan Ploski
Received on Fri Apr 22 19:39:55 2005

This is an archived mail posted to the Subclipse Users mailing list.