Plugins won't install on Eclipse

Question

I am trying to install subversive and checkstyle onto Eclipse IDE for Java Developers however the following message appears:

\"Cannot complete the install because on

Answer 1

Try running Eclipse as administrator, I just had the same issue and this worked for me.

Answer 2

Use eclipse update manager to install the plugins.. Then it will automatically select dependent plugins..You dont need to bother about dependent plugins in that case

Answer 3

I think you need the maven plugin in order to install your plugin. If that's the case, you can follow this this instruction to install it.

Answer 4

There's an alternative to running Eclipse as an administrator: you can manually give write permissions to your "eclipse" folder for all users (or just your current user). This way Windows/UAC won't pop up the security question that you see when you run programs as admin.

Answer 5

I had this problem, but I had to dig harder to fix it.

The source of my problem was the shortcut to launch Eclipse had this in the Target field:

"C:\Program Files\eclipse\eclipse.exe" -configuration C:\Program Files\eclipse\configuration

The problem with this is that without double quotes around the "-configuration C:\Program Files\eclipse\configuration" section it would hit that space in 'Program Files' and use C:\Program for storing configuration some of the time. Generally, if you have C:\Program you should make sure programs didn't put random files in there by mistake.

To fix this I had to move the configuration files from C:\Program to C:\Program Files\eclipse\configuration, picking and choosing along the way. Change the Target field to:

"C:\Program Files\eclipse\eclipse.exe" "-configuration C:\Program Files\eclipse\configuration"

and I was good to go.

Answer 6

All I had to do was completely open up full permissions for all users to the directory. This is dangerous if you have a multi-user system but Windows 7 seems to default to giving processes not very high permission levels; some processes (such as Eclipse Updated) don't know how to deal with this and request user permission, so they just bomb out. Easy fix: full control to all users and processes for the Eclipse Directory.