Eclipse Plugin Installation and Windows User Access Control
2016-03-13 14:45
169 查看
I make Eclipse Plugins and I sell them to developers using Eclipse. Most of the visitors to my web site are not Eclipse experts. One of my key challenges is getting them to successfully install and try my software. It sounds simple, but Eclipse plugin installation is somewhat complex and error-prone process.
The safest way to install a plugin in Eclipse is by using the update manager as opposed to using the Dropins folder or manually copying files. It is safer because Eclipse performs more checks to ensure everything is in order. For example, it can check that all the dependencies are met.
Lately, I got several reports from users who failed to install my plugin using the update manager. After some research and with the assistance of some devoted users, I located a major issue: Installing Eclipse plugins on Windows Vista & 7 with User Access Control (UAC) on, fails if Eclipse is installed in the Program Files folder.
It is a very common scenario: many users are already running Windows 7, the UAC is on by default and the Programs Files folder is where most of the applications are installed, especially custom Eclipse distros that come with fancy Installers. It is a frustrating issue because the plugin installation appears to be complete: it will not issue any error message and, after restarting the platform, it will even show up properly in the Installation Details box. However, the plugins and features JARs are not copies, hence the plugin in not installed.
There are several possible work arounds for this issue: (starting from the easiest)
Before the installation, start Eclipse with "Run as Administrator" option.
Turn off the pesky UAC (for the installation or, better yet, altogether).
Install Eclipse in a different folder. Eclipse doesn't have to be in the Program Files folder.
Switch to Linux or Mac.
Clearly, the way Eclipse is handling it is bogus and should be fixed. This problem has been around since the days of Vista and Eclipse 3.3. I understand that installing a plugin in this case is an issue, so the least Eclipse should do is fail the process and not mislead the non-suspecting user. If you agree, you might want to vote on this bug (there are several bugs on this topic).
PS. If you're looking for more useful tips on installing Eclipse plugins, check out this article. It was written for Galileo but still applies to Helios.
PS2. I know, I wrote an entire article on Eclipse plugins installation and never once mentioned P2. So, there, I mentioned it.
From http://blog.zvikico.com/2010/08/eclipse-plugin-installation-and-windows-user-access-control.html
The Java Zone is brought to you in partnership with ZeroTurnaround. Check out this 8-step guide to
see how you can increase your productivity by skipping slow application
redeploys and by implementing application profiling, as you code!
The safest way to install a plugin in Eclipse is by using the update manager as opposed to using the Dropins folder or manually copying files. It is safer because Eclipse performs more checks to ensure everything is in order. For example, it can check that all the dependencies are met.
Lately, I got several reports from users who failed to install my plugin using the update manager. After some research and with the assistance of some devoted users, I located a major issue: Installing Eclipse plugins on Windows Vista & 7 with User Access Control (UAC) on, fails if Eclipse is installed in the Program Files folder.
It is a very common scenario: many users are already running Windows 7, the UAC is on by default and the Programs Files folder is where most of the applications are installed, especially custom Eclipse distros that come with fancy Installers. It is a frustrating issue because the plugin installation appears to be complete: it will not issue any error message and, after restarting the platform, it will even show up properly in the Installation Details box. However, the plugins and features JARs are not copies, hence the plugin in not installed.
There are several possible work arounds for this issue: (starting from the easiest)
Before the installation, start Eclipse with "Run as Administrator" option.
Turn off the pesky UAC (for the installation or, better yet, altogether).
Install Eclipse in a different folder. Eclipse doesn't have to be in the Program Files folder.
Switch to Linux or Mac.
Clearly, the way Eclipse is handling it is bogus and should be fixed. This problem has been around since the days of Vista and Eclipse 3.3. I understand that installing a plugin in this case is an issue, so the least Eclipse should do is fail the process and not mislead the non-suspecting user. If you agree, you might want to vote on this bug (there are several bugs on this topic).
PS. If you're looking for more useful tips on installing Eclipse plugins, check out this article. It was written for Galileo but still applies to Helios.
PS2. I know, I wrote an entire article on Eclipse plugins installation and never once mentioned P2. So, there, I mentioned it.
From http://blog.zvikico.com/2010/08/eclipse-plugin-installation-and-windows-user-access-control.html
The Java Zone is brought to you in partnership with ZeroTurnaround. Check out this 8-step guide to
see how you can increase your productivity by skipping slow application
redeploys and by implementing application profiling, as you code!
相关文章推荐
- struts2 helloworld 的404错误
- java线程传统VS现代【3】
- java线程传统VS现代【2】
- java队列和栈的使用
- Java内部类的自我理解
- Java并发包中CyclicBarrier的工作原理、使用示例
- 20145221 《Java程序设计》第二周学习总结
- Eclipse/MyEclipse配置SVN插件
- 如何解决eclipse中没有plugin development
- Java遇见HTML——JSP篇之JSP基础语法
- Spring中配置数据源的4种形式
- IT十八掌作业_java基础第九天_多线程、自动拆装箱
- 解决:eclipse中jar包在外面显示
- spring笔记--依赖注入之针对不同类型变量的几种注入方式
- Spring AOP 实现原理与 CGLIB 应用
- 20145216史婧瑶《Java程序设计》第2周学习总结
- 20145216史婧瑶《Java程序设计》第2周学习总结
- eclipse 显示setting目录
- Java多线程
- 解决:eclipse报错:target runtime com.genuitec.runtime.generic.java is not defined