- This topic has 34 replies, 18 voices, and was last updated 16 years ago by
.
-
Posts
-
Lupestro,
The extension mechanism existed up to Eclipse 3.3 then was replaced in favor of the new /dropins support which is coming back at the end of January with a Pulse update. When the time comes, you should be able to grab the plugin and feature contents and literally drop them into a /dropins folder under MyEclipse to have it load those.
From MyEclipse 7.0 and onward we are not offering extended support for the older extension mechanism. On a side note most all ClearCase repositories will host-up the Eclipse Plugin for CC under a well-known location. There is an FAQ entry for that here: https://www.genuitec.com/forums/topic/clearcase-how-do-i-install-clearcase-in-myeclipse/
jeffmira & others,
There is a planned Pulse 2.4 update at the end of this month which (among many other things) adds back the support for the /dropins folder.
Will this update also restore the original Eclipse binary subdirectory within the MyEclipse install directory?
I’ve recently come across a need to load components from the base Eclipse installation to perform code formatting in a ‘batch’ type mode outside any IDE.
Will this update also restore the original Eclipse binary subdirectory within the MyEclipse install directory?
No, file layout on disk will stay the same.
Vince & Others getting prompted over-and-over for proxy authentication. This was specifically one of the NTLM-related proxy bugs we fixed in 7.0.1, the workaround to get it to stop prompted and work (and subsequently pickup the 7.0.1 update and work forever there after) is as follows:
=====================
If you have previously saved credentials, you will need to delete the file
stored in:
<MyEclipse Install Dir>/Common/configuration/com.genuitec.pulse2.common.http/connection.storageThis will remove any cached credentials and allow you to finish using the services you desire, as long as you don’t save credentials for your NTLM proxy server again until after the 7.0.1 update is applied.
=====================As it turns out the bug was related to how we were retrieving the stores credentials — we were doing it wrong resulting in never-ending prompts. This was just occuring with NTLM proxies though and should be fixed with the workaround and 7.0.1 update.
