the problem that the button tries to open the "general" category in the options
dialog which is, unfortunately, already opened behind the modaly opened "manage
connections settings". Feels like trying to bite my own ... .

i guess that the first thing to do would be to find a reasonable solution for
this from the UI point of view:
- open the dialog again
- close the manage settings dialog
- remove the proxy button, or eventually get rid of the whole dialog:)

pepa - any ideas?

since th ecentralized proxy administration we don't need the button at all

fixed

Checking in wizards/repositorystep/RepositoryStep.java;
/cvs/subversion/main/src/org/netbeans/modules/subversion/ui/wizards/repositorystep/RepositoryStep.java,v
 <--  RepositoryStep.java
new revision: 1.41; previous revision: 1.40
done
Checking in repository/Repository.java;
/cvs/subversion/main/src/org/netbeans/modules/subversion/ui/repository/Repository.java,v
 <--  Repository.java
new revision: 1.55; previous revision: 1.54
done

Verified in Build 200703272330.

*** Issue 99639 has been marked as a duplicate of this issue. ***

*** Issue 99639 has been marked as a duplicate of this issue. ***

I still have the problem that when I go to Options -> Miscellaneous -> Versioning -> Subversion -> Manage Connection Settings... -> Proxy Configuration...
the button for the proxy configuration exists, but does not work when I click it. I need to set an exception for the proxy usage (I already configured the proxy correctly for Netbeans in the "General" settings tab, but that does not seem to work for subversion). If I try to use subversion I get an error message: "OPTIONS of '[MYURL]': Could not create SSL connection through proxy server: 403 Forbidden ([MYURL])"
However, subversion shouldn't use the proxy since the url is in the exception list (at least for Netbeans, but obviously not for subversion).

BTW, I'm using:
Product Version: NetBeans IDE 6.7 (Build 200906241340)
Java: 1.6.0_12; Java HotSpot(TM) Client VM 11.2-b01
System: Windows Vista version 6.0 running on x86; Cp1252; de_DE (nb)

Please attach ~/.netbeans/6.7/config/svn/config/servers file. Could you also try the latest dev build (or 6.8 beta)? I fixed a similar issue (bug 170264) about 2 months ago.
Also attach the message log with the error (~/.netbeans/6.7/var/log/message.log).

Hi, 
thanks for the quick reply.
The error log just adds the following lines, when I try to open the proxy settings dialogue (note that I removed private company information and replaced it by [SOMETHING]):

WARNUNG [org.openide.filesystems.Ordering]: Not all children in OptionsDialog/ marked with the position attribute: [FontsAndColors, General, Keymaps, org-netbeans-modules-php-project-ui-options-PHPOptionsCategory], but some are: [Actions, Advanced, Editor, PreviewExamples, General.instance, Editor.instance, FontsAndColors.instance, Keymaps.instance, org-netbeans-modules-php-project-ui-options-PHPOptionsCategory.instance, Advanced.instance]
INFO [org.netbeans.modules.mercurial]: Could not load the file [HOME]\Mercurial.ini. Falling back on hg defaults.
WARNUNG [org.netbeans.api.options.OptionsDisplayer]: Options Dialog is opened

And for each click on the button "Proxy configuration..." the last line is added to the log:
WARNUNG [org.netbeans.api.options.OptionsDisplayer]: Options Dialog is opened

But there's no window opening where I could edit anything. The button click just has no effect (seemingly).

The servers file just contains the lines:
[global]
http-proxy-host = [PROXYSERVER]
http-proxy-port = 8080

So there are no exceptions listed for the proxy.

When I try to annotate a file, the following is logged:

INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: OPTIONS of '[URLOFJAVAFILE]': Could not create SSL connection through proxy server: 403 Forbidden ([PROXYSERVER])"
INFO [org.netbeans.modules.subversion]: svn: OPTIONS of '[URLOFJAVAFILE]': Could not create SSL connection through proxy server: 403 Forbidden ([PROXYSERVER])
org.tigris.subversion.svnclientadapter.SVNClientException: svn: OPTIONS of '[URLOFJAVAFILE]': Could not create SSL connection through proxy server: 403 Forbidden ([PROXYSERVER])
	at org.netbeans.modules.subversion.client.cli.CommandlineClient.checkErrors(CommandlineClient.java:777)
	at org.netbeans.modules.subversion.client.cli.CommandlineClient.exec(CommandlineClient.java:755)
	at org.netbeans.modules.subversion.client.cli.CommandlineClient.annotate(CommandlineClient.java:637)
	at org.netbeans.modules.subversion.client.cli.CommandlineClient.annotate(CommandlineClient.java:633)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.netbeans.modules.subversion.client.SvnClientInvocationHandler.handle(SvnClientInvocationHandler.java:271)
	at org.netbeans.modules.subversion.client.SvnCmdLineClientInvocationHandler.invokeMethod(SvnCmdLineClientInvocationHandler.java:77)
	at org.netbeans.modules.subversion.client.SvnClientInvocationHandler.invoke(SvnClientInvocationHandler.java:127)
	at $Proxy11.annotate(Unknown Source)
[catch] at org.netbeans.modules.subversion.ui.blame.BlameAction.computeAnnotations(BlameAction.java:164)
	at org.netbeans.modules.subversion.ui.blame.BlameAction.access$000(BlameAction.java:68)
	at org.netbeans.modules.subversion.ui.blame.BlameAction$1.perform(BlameAction.java:145)
	at org.netbeans.modules.subversion.client.SvnProgressSupport.performIntern(SvnProgressSupport.java:103)
	at org.netbeans.modules.subversion.client.SvnProgressSupport.run(SvnProgressSupport.java:96)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:577)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1030)

But this error just seems to be the usual error, since our proxy doesn't allow that connection.

Unfortunately I cannot try any new Netbeans versions at the moment (maybe at some later point), since I don't have the time. Sorry.

Some further information: a colleague is using Netbeans 6.5 (with Vista) and has the same problem while another colleague is using 6.7 (with XP) and there the problem does *not* occur. So maybe it's Vista specific.

The 'Proxy configuration' button is just a shortcut to Options>General>Proxy settings, so if you want to set those settings, go directly there.

You say you already set a host-exception to proxy settings. Did you set the proxy settings to 'Manual settings' in the 'General' tab and then add a host to 'No Proxy Hosts' in the Advanced dialog (displayed after clicking on 'More...')?

Oh, a shortcut to something you cannot go, because the window with that button is keeping the user from seeing it. Interesting. ;-)
Maybe instead of the button a hint that the global proxy settings will be used would be better.

Any way, yes, I set it to manual and in the "no proxy hosts" the correct value was set, but it still didn't work.
I just found out how to make it work, though. When I edited something in the "no proxy hosts" and clicked on save, it worked. So, for some reason the string displayed there wasn't actually the string taken by Netbeans. And only after editing the string and clicking on save it was actually used.

The button is mainly to be used from the checkout dialog (that's what it used for and there the button works). It is a defect that is is visible in the Options dialog.

fixed: cdev #786afd8fa4e7

The button 'Proxy settings' is no longer visible in Options dialog.
About your WA: you're right, everything starts working when you edit the exception list in global options. I'll try to fix subversion so the WA won't be needed.

Integrated into 'main-golden', will be available in build *200911241400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/786afd8fa4e7
User: Ondrej Vrabec <ovrabec@netbeans.org>
Log: Issue #98319 - Proxy Configuration button doesn't work in SVN Options
Disabling 'proxy settings' button in Options

AFAIK this should be already fixed by core-main #3afc9d172e12