| Classic Update in Juno [message #894991] |
Wed, 11 July 2012 07:02  |
Eclipse User |
|
|
|
In my project we control the plug-ins through the "Manage Configuration" possibility. Downloaded plu-ins etc. are loaded thorugh an extension point from a file location (managed by SVN)
This has proven to be a reliable way of making sure all developers in a team share the same configuration.
I am now updating our project to Juno, and even after enabling the "Classic Update" in preferences, the menu item Help->Software Update->Manage Configuration is missing.
It also seems to be missing in the documentation for juno at http://help.eclipse.org/juno/index.jsp
Any help?
|
|
|
|
|
| Re: Classic Update in Juno [message #895287 is a reply to message #895212] |
Thu, 12 July 2012 07:43  |
| Eclipse User |
|
|
|
Adding things to /features and /plugins will work ... sometimes, but it is definitely not recommended, not supported, and can break on the slightest change.
What you want can be done with p2. When I unzip a new eclipse installation, I run the director to add all of the other features I need. ex:
eclipse/eclipse \
-application org.eclipse.equinox.p2.director \
-noSplash \
-repository \
http://download.eclipse.org/egit/pde/updates-nightly,\
http://download.eclipse.org/egit/updates-nightly,\
http://download.eclipse.org/eclipse/updates/4.2-I-builds,\
http://download.eclipse.org/e4/updates/0.12-I-builds,\
http://download.eclipse.org/modeling/emf/emf/updates/2.8milestones,\
http://download.eclipse.org/releases/juno,\
http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository,\
file://$HOME/eclipseUpdate \
-installIUs \
org.apache.commons.jxpath/1.3.0.v200911051830,\
org.apache.batik.xml/1.6.0.v201011041432,\
org.dojotoolkit/1.6.1.v201105210659,\
org.eclipse.nebula.widgets.gallery/1.0.0.R_0_20090212,\
org.eclipse.egit.feature.group,\
org.eclipse.egit.source.feature.group,\
org.eclipse.jgit.feature.group,\
org.eclipse.jgit.source.feature.group,\
org.eclipse.egit.fetchfactory.feature.group,\
org.eclipse.emf.sdk.feature.group,\
org.eclipse.pde.api.tools.ee.feature.feature.group,\
org.eclipse.xtext.sdk.feature.group,\
org.eclipse.e4.core.tools.feature.feature.group,\
org.eclipse.e4.tools.css.editor.feature.feature.group,\
org.eclipse.e4.tools.css.spy.feature.feature.group,\
org.eclipse.wst.xml_ui.feature.feature.group,\
org.eclipse.e4.oome.feature.group
There are tools available that can provide one repo that points to a bunch of other repos (one stop shopping), tools that can collect the features and plugins you need from multiple existing repos into a local (to your company) reference repo, and tools that can take existing groups of features/plugins and publish them as a local repo.
PW
|
|
|
| Re: Classic Update in Juno [message #897321 is a reply to message #895212] |
Mon, 23 July 2012 11:12 |
| Eclipse User |
|
|
|
On 12.07.2012 08:53, Morten Frank wrote:
> Thanks for the answer.
>
> It is then still a bit puzzling, that the possibility to select
> "Classic update" is still present in Preferences -> General ->
> Capabilities
See https://bugs.eclipse.org/369540
Dani
>
> Anyway, we settled on a procedure, where a script unzips the eclipse
> installation and copies /features and /plugins from a reference
> installation.
> Not as nice as an extension point, but it works.
>
> In general I find Eclipse to be the best development tool around for
> Java development, but also the hardest one to keep in a consistent
> state for a team of developers.
>
> /M
|
|
|
Powered by
FUDForum. Page generated in 0.08365 seconds
Home