Unable to load default SVN client

-
While installing the subversion plugin Subclipse in the Eclipse IDE I came across a problem. Subclipse uses "JavaHL (JNI)" to interface with subversion by default.

Initially I was getting the following error message when accessing Windows->Preferences->Team->SVN->SVN Interface dropdown:
JavaHL (JNI) Not Available



When attempting to view a repository via the "SVN Repository Exploring" perspective I got a different error message:
Unable to load default SVN client


So I installed the below package
sudo apt-get install libsvn-java


Still the problem continued and I realized that I need to provide the liberary to Eclipse (3.6 Helios)

I choose to set the path to the JavaHL libraries via a command line argument. I accomplished this by setting my Launcher icon for Eclipse to use the command

/path/to/eclipse -vmargs -Djava.library.path=/usr/lib/jni


Another option is to set the LD_LIBRARY_PATH environment variable to point to the /usr/lib/jni in your .profile file. Add the below line:

export LD_LIBRARY_PATH='/usr/lib/jni'


Once that was done I was able to set the SVN repository successfully. But one last challenge was left. When I was browsing the repository, It was continuously asking me for the password. Somehow Eclipse keyring was not able to store the password.

To resolve this I changed the SVN Interface setting in Windows->Preferences->Team->SVN->SVN Interface dropdown from JavaHL to SVNKit and finally it all worked.

Comments

  1. AnonymousJune 7, 2011 at 9:42 AM

    Thanks.. the last bit on setting to SVNKit did the trick.

    ReplyDelete
  2. AnonymousJuly 30, 2011 at 7:10 AM

    Thanks. very helpful

    ReplyDelete

Post a Comment

Popular posts from this blog

Hibernate: a different object with the same identifier value was already associated with the session

-
People working with Hibernate might be familiar with the below error. org.springframework.orm.hibernate3.HibernateSystemException: a different object with the same identifier value was already associated with the session: nested exception is org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session This exception is generated when we try to load an instance object in session which has been already loaded by hibernate. Easier said than done. Hibernate considers two persistent entities identical if the two rows of the table can be said identical. Above error could be generated in many ways and there may be various solutions on net like using session merge etc to get away with the problem. I will discuss here the reason for me getting this problem and the way I resolved it. Below is the code which generated the exception for me. Following is the method which caused the exception @Transactional(propagation=Propagation....
Read more

BeanDefinitionStoreException: Failed to parse configuration class: Could not find class [javax.jms.ConnectionFactory]

-
If you are creating a Spring Boot application and see the following error stack . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.2.0.RELEASE) 2020-06-27 19:30:32.786 INFO 35224 --- [ main] SchoolApplication : Starting SchoolApplication on LTUS76179 with PID 35224 (C:\personal\eclipse-workspace\apievolution\target\classes started by 381548 in C:\personal\eclipse-workspace\apievolution) 2020-06-27 19:30:32.796 INFO 35224 --- [ main] SchoolApplication : No active profile set, falling back to default profiles: default 2020-06-27 19:30:32.964 WARN 35224 --- [ main] ionWarningsApplicationContextInitializer : ** WARNING ** : Your ApplicationContext is unli...
Read more

org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]

-
This Exception during the maven build in an hibernate based project could come due to various reasons. Primarily one should look into the complete stack trace. The further exception usually do give clue of the actual problem. I my case, the stack trace revealed the below issue Exception in thread "main" org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer] at org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:110) at org.hibernate.tuple.entity.EntityTuplizerFactory.constructDefaultTuplizer(EntityTuplizerFactory.java:135) at org.hibernate.tuple.entity.EntityEntityModeToTuplizerMapping. (EntityEntityModeToTuplizerMapping.java:80) at org.hibernate.tuple.entity.EntityMetamodel. (EntityMetamodel.java:323) at org.hibernate.persister.entity.AbstractEntityPersister. (AbstractEntityPersister.java:456) at org.hibernate.persister.entity.SingleTableEntityPersister. (SingleT...
Read more