Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 358266

Summary:	Augment defaults.pref to allow adding plug-ins on the same server in a seamless way
Product:	[ECD] Orion	Reporter:	Szymon Brandys <Szymon.Brandys>
Component:	Client	Assignee:	Silenio Quarti <Silenio_Quarti>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P4	CC:	eclipse, gorkem.ercan, mamacdon, pedemont, simon_kaegi, snorthov
Version:	0.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Szymon Brandys

2011-09-20 11:46:37 EDT

This is my case:
1) I have Orion and some SCM client for Orion hosted on the same server
2) The SCM client provides a plug-in with an extension to the file navigator 

To see the extension, one needs to know the plug-in URL and then register it on the Orion plug-ins page. Since Orion and SCM client are hosted on the same server maybe we could register the plug-in in Orion in some seamless way?

Comment 1 Simon Kaegi

2012-10-03 16:19:54 EDT

Untargetting and tempted to say WONTFIX. A custom install might want to do this but I suspect it just complicates things. A marginally better approach might be a mechanism to pre-populate user settings as opposed to using defaults for that purpose.

Comment 2 Simon Kaegi

2013-06-10 15:24:27 EDT

*** Bug 404715 has been marked as a duplicate of this bug. ***

Comment 3 Rafael Chaves

2014-05-02 09:53:52 EDT

Bug 380809 is another duplicate (or data point).

Comment 4 Gorkem Ercan

2015-04-16 13:48:27 EDT

I think this is preventing the orion java server bits to be consumed directly. For instance I am force to use a filter because I do not want to fork orion to get my client plugins to be on by default. 

IMHO there should be a mechanism to aggregate default active client plugins from the server pieces, that may eliminate the need to maintain a .pref file completely and give to responsibility to server pieces.

@Simon do you think this makes sense? I probably can come up with a patch for this


[1] https://github.com/gorkem/orion-openshift/blob/master/bundles/org.jboss.orion.openshift.server.core/src/org/jboss/orion/openshift/server/core/OpenshiftDefaulsPrefs.java

Comment 5 John Arthorne

2015-05-05 16:30:24 EDT

This open bug report had a target milestone in the past. The target milestone has been removed. Please target for a date in the future or leave the target blank if it is not known.

Comment 6 John Arthorne

2015-05-28 14:34:29 EDT

(In reply to Gorkem Ercan from comment #4)
> IMHO there should be a mechanism to aggregate default active client plugins
> from the server pieces, that may eliminate the need to maintain a .pref file
> completely and give to responsibility to server pieces.

I'm not convinced this can be decentralized.. it is a "product level" decision. I think every component/plugin would say "my plugin should be included by default" but a product may not want it. Something like a server configuration setting specifying location of the plugin list could work.

Comment 7 Michael Rennie

2017-01-10 15:46:08 EST

Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html

Comment 8 Rafael Chaves

2017-01-11 13:54:06 EST

Reopening as suggested.

Comment 9 Michael Rennie

2018-04-09 09:40:09 EDT

Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. 

For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04114.html