Community
Participate
Working Groups
I discussed this with Pawel: The reason we create executable extension so early is that Authenticator provided by ui.net is consumed by java.net. The code calling Authenticator is out of our jurisdiction and we don't have a clue when it's first needed. One suggestion from Pawel is: On the other hand we could register an authenticator from core.net (with no UI dependency) and when after it's called create an extension and delegate the call to ui.net This is related to bug313741. For now we are working around the issue in p2. I don't think anything like the suggestion from Pawel should be attempted in 3.6.
Created attachment 179641 [details] patch It is a patch which separate authentication from UI to core. UI provides only a dialog if a password is needed. The next step is to provide credentials from secure preferences to avoid displaying dialog in UI if credentials are stored (bug 312228).
Wojtek, please sync the patch with HEAD.
Created attachment 180890 [details] patch for head
I am no longer involved in Platform Team/Compare development.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
