The compares (base, latest) both think it's unchanged.
That's ok - I guess this is an eclipse bug rather than a subclipse bug; I'll
try lodging something there.
Cheers,
Nigel
On 27/07/07, Mark Phippard <markphip@gmail.com> wrote:
>
> On 7/27/07, Nigel Magnay <nigel.magnay@gmail.com> wrote:
> > I think the file may well have been modified outside eclipse, so your
> > assessment sounds right - but it's still a bit scary to click on an
> > individual file that I know has changed and have eclipse tell me 'nope -
> > still the same'.
> >
> > I've done refresh on both the working set, and the individual project
> (and
> > by multi-selecting all the projects and clicking refresh) and it still
> > doesn't think there are changes.
>
> You should do Compare with Base if you want to verify your changes.
> Just on the off chance the repository file has been changed since
> checkout.
>
> I do not what else to tell you. When you take one of these options,
> we go get the thing you choose to compare against and then point
> Eclipse at it. The Eclipse compare engine does the rest.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
Received on Fri Jul 27 13:23:13 2007