search

yuanshuo / jupiter-eclipse-plugin

Automatically exported from code.google.com/p/jupiter-eclipse-plugin
0 stars 0 forks source link

Review file not marked as modified in subclipse #36

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create any new jupiter issue
2.
3.

What is the expected output? What do you see instead?
When I look in the eclipse project window, I expect to see that the review
file is modified and I need to check in my change. Instead, in the eclipse
window shows that the review file is unmodified. If I open windows explorer
and go to the file where the review is saved, it does show the file as
modified in tortiose svn. 

What version of the product are you using? On what operating system?
Jupiter 3.3.1 in Eclipse 3.3 with the subversion plug-in subclipse on
Windows NT

Please provide any additional information below.
Thanks in advance!

Original issue reported on code.google.com by claretri...@gmail.com on 12 Jun 2008 at 9:16

GoogleCodeExporter commented 9 years ago 
Technically this isn't really a bug.  This is just how it is.  The way Eclispe 
works
is when any file gets modified "outside" of the Eclipse system Eclipse doesn't
refresh automatically to see if any of the files got modified.  That is unless 
you
enable Refresh Automatically.

All Jupiter files are modified using plain Java classes and none of that goes 
through
the Eclipse system.  This is why Eclipse doesn't know they've been modified 
since
Eclipse doesn't go to check if any files have been modified.  It does get 
refreshed
if Refresh Automatically is on.

I normally don't do issues that deal with some other Eclipse plugin that isn't
bundled readily with the downloadable versions of Eclipse.  I may make an 
exception.
 I might be able to force a full refresh of the project programatically but I make no
promises.

Remarking as enhancement.  Scheduling for 3.4.  Priority will be low.

Original comment by jsakuda on 14 Jun 2008 at 10:42

GoogleCodeExporter commented 9 years ago 
Thanks for the explanation - I didn't appreciate the "inside" vs "outside"
distinction but it does make sense - after all, if I modify in notepad I have to
refresh in eclipse too.

I like your idea of automatically refreshing but I wouldn't want a full project
refresh as that takes about minute to complete. From the GUI I can refresh just 
one
file - could you do that automatically from the java side?

Are you sure "low" is the right priority? This does hinder the usability...

Thanks again!

Original comment by claretri...@gmail.com on 14 Jun 2008 at 2:06

GoogleCodeExporter commented 9 years ago 
I may be able to refresh one file, I'm not certain.  I have marked it low 
because
this doesn't affect all users, mostly those with subclipse.  Don't fear though, 
I
will fix it for the next release.  I'm not sure when the release will be out 
though
since 3.3.1 just came out and I'm waiting for Ganymede's final release.

Original comment by jsakuda on 14 Jun 2008 at 11:15

GoogleCodeExporter commented 9 years ago 
I found the solution on how to refresh single files.  The FAQ page is here:
http://wiki.eclipse.org/FAQ_When_should_I_use_refreshLocal%3F.

I have tested this with the .review files and it is working.  Expect this fix 
to be
in the next release!

Original comment by jsakuda on 25 Jul 2008 at 8:51

GoogleCodeExporter commented 9 years ago

Original comment by jsakuda on 25 Jul 2008 at 8:51

GoogleCodeExporter commented 9 years ago 
Fixed in Revision 126.  Forcing programmatic refresh of Jupiter created files.

Original comment by jsakuda on 25 Jul 2008 at 9:56