This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of DevSecOps Adventures: A Game-Changing Approach with Chocolate, LEGO, and Coaching Games and have Dana Pylayeva on-line!
See this thread for details.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Tim Cooke
Sheriffs:
  • Rob Spoor
  • Liutauras Vilda
  • paul wheaton
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Mikalai Zaikin
  • Carey Brown
  • Piet Souris
Bartenders:
  • Stephan van Hulst

Loading Plugins and maintaining the Eclipse Environment

 
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I usually download the plugin zip file and manually install it into the appropriate folder.
I do this so I have a copy of the plugin. It looks like directly loading using the Update Manager would not give me a copy.
I have had to reload Eclipse a couple of times so I try to keep it easy to recreate my current environment.
 
Ranch Hand
Posts: 2379
MySQL Database Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jim, I am not sure but update manager should download a zipped plugin anyway that should be reusable.
 
Author
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This whole area of installing plug-ins is tricky.
First-off, if you used Update Manager to install a feature and its associated plug-ins, they are installed on your machine. The update manager downloads them from the URL you opened (where a site.xml file was found to define the features that could be installed) and then writes them to the install site you identified.
The default install site is the current Eclipse directory. This means they are just added to your current \features and \plugins dirs. With this choice, every workspace you open will 'see' those plug-ins. If you choose a new install site for update manager to use then the features/plugins installed are only visible to the workspace you used during the install. If you look down in the workspace/.metadata/.config dir you would fine a file named platform.cfg that is the workspace memory of that Update Manager install.
That said, you can dump plug-ins (and I hope a feature too) into the eclipse\plugins and eclipse\features directories, but I wouldn't...
The right approach depends on what you want to do and is it for one workspace or the full eclipse install. This is a detailed discussion, and one I'll post soon as a new entry.
 
He got surgery to replace his foot with a pig. He said it was because of this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic