Mark Phippard wrote:
>
> Are you saying this is a behavior change from 1.2.0? That seems hard
> to believe unless you are using SVNKit and they were not throwing this
> error before. I know that JavaHL does, so it seems unlikely.
>
Sorry, I made an incorrect assumption. It started when I began to use
the location to obtain the adapter (of course, since no listener was
added before). It happens regardless of version.
>
>> 2. How do I avoid that messages are printed?
>
> Create your own ISVNNotifiyListner and add it to the ISVNClientAdapter
> you get. See this Subclipse example:
>
> http://subclipse.tigris.org/source/browse/subclipse/trunk/subclipse/core/src/org/tigris/subversion/subclipse/core/client/PeekStatusCommand.java?rev=2716&view=markup
>
Thanks. This helped me understand where the messages came from. My
solution was to remove the listener that was added by the adapter
getSVNClient() call. Like this:
clientAdapter.removeNotifyListener(NotificationListener.getInstance());
Regards,
Thomas Hallgren
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Mon May 7 22:06:34 2007