Hi Mark,
As I have no knowledge on Eclipse API in general, I still do not
thoroughly understand the discussion on the root cause of the issue,
whether it is Subclipse or Eclipse responsibility. If you think there is
still some issue with their suggestion, should we continue the
discussion there? Or do you think we we should better file an issue in
Subclipse and find some time to take care of it later? However, as you
suggested, I think the issue should be given some priority as it could
cause users to lost their data without knowing.
Regards,
Vairoj
Mark Phippard wrote:
> "Vairoj A." <vairoj@hotpop.com> wrote on 09/24/2006 11:31:43 PM:
>
>
>> Since it was concluded from the Eclipse Bugzilla that the behavior is
>> "as expected behavior" from Eclipse API perspective, do you think that
>> the issue should be solved within Subclipse?
>>
>
> I do not see why they closed the issue given that they do not really offer
> a decent API we can call. I tried the API they suggested and it did not
> seem to work. That being said, it is easy to get confused by this issue,
> so maybe it did.
>
> Regardless, as I was coding the API I could see right away that it was not
> something I would leave in. For one thing, if the revert command failed
> for some reason we would have wiped out your source. Presumably the old
> version could be retrieved from local history.
>
> You can file an issue in our issue tracker if you like. I do not see
> myself coming back to it for a while though. However, someone else might.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Sep 26 09:53:21 2006