- This topic has 9 replies, 9 voices, and was last updated 20 years, 11 months ago by
.
-
Posts
-
I think I need a little more detail to determine what’s being requested here. Can you provide more detail around a usage case or liken it to a similar Java editor behavior?
–Scott
MyEclipse Supportjsp editor should trigger source control check-in on modification like keystroke of copy/paste…
Sounds a little extreme to me, this isn’t at all like the default behaviour for java files (they merely compile on save). So I wouldn’t say should, however, it might be an interesting option: I’ve always favoured having options which reflected how people work (or would like to work) rather than enforcing a way of working on others. After all, one man’s intuitive behaviour is another’s nightmare… 🙂
Ciao,
Mark.
This behavior is the standard behavior for java editor and many other.
For files under source control (in my case it is clearcase), when a modification is done on a file (key stroke, copy/paste, delete, internal editing due to refactoring for example) the source control plug-in is trigerred and ask if the file should be reserved (the plug-in behavior is set in it’s own option configuration) if not already reserved.
I known the reservation mechanism is not common for all source control software but they all need to be aware of a file modification…
I use the VSS plugin and the behaviour is the same. When I click on a .java file it asks me whether I want to check the file out for editing. But this is not triggered for a .jsp file (it just asks me whether I want to reset the read only flag). I don’t know whether this is a problem in the plugin or in the JSP editor.
I happen to use a source control system at the moment that requires me to check file out before I can change them. If I open a JSP file in the JSP editor, then check it out, the file does not become writable in the editor, making it necessary to close the editor and open again to make any changes. This is even more inconvenient than just having to check the file out before I can change it. The behavior of the platform text editor should be standard here. You can test it out by using the “Open With” sub-menu and opening a JSP file with the default text editor.
Thanks for this feedback. Being a CVS-based environment these issues are harder to identify. I have entered this in our issues tracking system to be researched very shortly.
Michael
MyEclipse SupportThis checkin-on-change behavior seems pretty antiintuitive… for example, if you have CVS decorations on, and edit a file, your project tree view will visually update showing changes that should/need to be committed to the repository… but you are saying with some of these other source control mechanisms, a simple change in a file triggers not only that, but a dialog asking if you want to reserver (or checkin) the file?
What if you are working on 1 2000 line file all day long… is it constantly asking you? (Sorry, I’m a CVS-inbred)
@cagatayk wrote:
I happen to use a source control system at the moment that requires me to check file out before I can change them. If I open a JSP file in the JSP editor, then check it out, the file does not become writable in the editor, making it necessary to close the editor and open again to make any changes.
I second that request. VSS has all local files read-only until they’re checked out. With the VSS plugin (http://sourceforge.net/projects/vssplugin, as soon as you attempt to change text in a Java file that’s not checked out, a pop-up asks if you want to check it out. If you do, the file is immediately checked out and the keystroke or other edit you initiated is completed, if not, it asks if you want to unset the read-only flag (which I assume is default Eclipse behavior when editing a read-only file). It would be great if the JSP editor supported this.
-john.
