o.n.m.subversion.Annotator.getActions(...) could be a good entry point
- create your own action. Subclass from ContextAction if it's supposed to be context sensitive - e.g. IgnoreAction or StatusAction are simple enough and should give you an idea what to do.
- add it to the list returned in getActions(...) - once for main menu and once for the context menu

So how long do we have to wait?!
It is a simple issue, could be solved really easy, and we've been waiting 4 years already!
Could I tell my grand children this is something they can expect to be blessed with? :)

The proposal sounds very good, indeed it is way overkill for our needs. The On demand locking should be default off, if you ask me. There usually is a good reason for setting the "needs-lock" property. Furthermore, don't contact the server unless requested - most files are not locked and we don't need more lag in Netbeans :)

Tested on my system:
Product Version: NetBeans IDE Dev (Build 201106080600)
Java: 1.6.0_24; Java HotSpot(TM) 64-Bit Server VM 19.1-b02
System: Windows 7 version 6.1 running on amd64; Cp1252; no_NO (nb)
Works smoothly, including the editor switching to/from readonly-mode nicely.
One issue: No errors/messages are shown if it fails - neither as an error dialog (preferrable), or as a message in the IDE status bar. In my case it failed because of an authentication issue. When I tried commit'ing instead, I got the authentication dialog (as I should). After authenticating it worked.
Well done! Please add some error handling and it is good for 7.1!

(In reply to comment #31)
> neither as an error dialog (preferrable)
i am against, raising a dialog for a background task (that is not triggered by an explicit user action) is IMO a bad idea. Especially to users who might not expect it, this could be really troublesome. For example in case you are not connected to network.
> or as a message in the IDE status bar
That's an option, plus can be logged in the output window

(In reply to comment #32)
> (In reply to comment #31)
> > neither as an error dialog (preferrable)
> i am against, raising a dialog for a background task (that is not triggered by
> an explicit user action) is IMO a bad idea. Especially to users who might not
> expect it, this could be really troublesome. For example in case you are not
> connected to network.
> > or as a message in the IDE status bar
> That's an option, plus can be logged in the output window
I agree, sort of, but this was not a background task, it was triggered by me choosing the "Lock" command. (Can this be started as background task?? I'm against)
However, I didn't check the output window, so I checked it now, and it doesn't make sense:
==[IDE]== 09.jun.2011 14:47:43 Locking Files...
lock -m "i need lock" myfile.xml
Autorisasjonen feilet
svn: User canceled dialog
But I didn't get any authentication dialog!? (Btw: "Autorisasjonen feilet" means "Authentication failed", don't know why it shows in Norwegian)