Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » Classic Update in Juno(Missing the entry in help menu)
Classic Update in Juno [message #894991] Wed, 11 July 2012 11:02 Go to next message
Morten Frank is currently offline Morten Frank
Messages: 2
Registered: July 2012
Location: Denmark
Junior Member
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 #895120 is a reply to message #894991] Wed, 11 July 2012 18:12 Go to previous messageGo to next message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

The legacy update manager was removed in juno. It only works with the new p2/install manager story.

There are a couple of ways to distribute plugins to development teams, depending on what you start with and where you keep the plugins (shared drive, web server, etc).

PW


Re: Classic Update in Juno [message #895212 is a reply to message #895120] Thu, 12 July 2012 06:53 Go to previous messageGo to next message
Morten Frank is currently offline Morten Frank
Messages: 2
Registered: July 2012
Location: Denmark
Junior Member
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

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
Re: Classic Update in Juno [message #895287 is a reply to message #895212] Thu, 12 July 2012 11:43 Go to previous messageGo to next message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

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 15:12 Go to previous message
Dani Megert is currently offline Dani Megert
Messages: 3801
Registered: July 2009
Senior Member
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
Previous Topic:Can't create new java project
Next Topic:Updating document partitioning according to data structure update
Goto Forum:
  


Current Time: Sun Oct 26 00:25:27 GMT 2014

Powered by FUDForum. Page generated in 0.08788 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software