[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subclipse-dev
Subject:    Re: internal error when fetching resource history
From:       Eugene Kuleshov <eu () md ! pp ! ru>
Date:       2005-09-20 3:51:31
Message-ID: 432F8743.5090807 () md ! pp ! ru
[Download RAW message or body]

Mark,

   I think I fixed this now. The problem was that ResourceTransfer 
wasn't restoring last changed revision, so search was failing. See issue 
318 (which I've reopened) for some additional comments and a patch for 
ResourceTransfer.

http://subclipse.tigris.org/issues/show_bug.cgi?id=318

   regards,
   Eugene


Mark Phippard wrote:
> "Georg-W. Koltermann" <Georg.Koltermann@mscsoftware.com> wrote on 
> 09/14/2005 03:03:13 AM:
> 
> 
>>I am getting an internal error when from the repository exploring 
>>perspective when I drag a file entry from the repository tree onto the 
>>resource history window.  The error in the log is:
>>
>>!ENTRY org.eclipse.core.runtime 4 2 2005-09-14 08:52:45.593
>>!MESSAGE An internal error occurred during: "Fetching SVN revision 
> 
> history".
> 
>>!STACK 0
>>java.lang.ArrayIndexOutOfBoundsException: -1
>>        at org.tigris.subversion.subclipse.core.commands.GetLogsCommand.
>>getUrls(GetLogsCommand.java:122)
>>        at org.tigris.subversion.subclipse.core.commands.GetLogsCommand.
>>createLogEntriesForFile(GetLogsCommand.java:195)
>>        at org.tigris.subversion.subclipse.core.commands.GetLogsCommand.
>>run(GetLogsCommand.java:76)
>>        at 
> 
> org.tigris.subversion.subclipse.core.resources.RemoteResource.
> 
>>getLogEntries(RemoteResource.java:195)
>>        at org.tigris.subversion.subclipse.ui.history.
>>HistoryView$FetchLogEntriesJob.run(HistoryView.java:1237)
>>        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
>>
>>
>>Note that it works fine when I select "show in resource history" from 
>>the context menu.  The error just occurs when I use drag and drop.
>>
>>Eclipse 3.1, FreeBSD 5.4, subclipse 0.9.34 using JavaHL, svn 1.2.3.
> 
> 
> I was hoping Eugene Kuleshov would jump in since he added this feature.  I 
> cannot think of why it would work one way and not the other.  Would you 
> mind filing a bug in our issue tracker?
> 
> Thanks
> 
> Mark

[prev in list] [next in list] [prev in thread] [next in thread]