| 3.0 sharedsite configuration/user preferences/launch arguments [message #254307] |
Mon, 21 June 2004 16:26 |
 Bernard Cena
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
I've been scanning through the additions for v.3.0 wrt Eclipse support for
shared (read-only) installations, shared user preferences and launch
command line arguments - could someone please summarise what the changes
are "in a nutshell" and perhaps provide references to relevant pages.
Specifically:
1) what is the 3.0 preferred way to make plug-ins available in a shared
read-only environment ?
2) what is the 3.0 preferred way to define global user (eg. editor)
preferences on a shared read-only environment ?
3) what are the launch command line arguments for eclipse to manage
read-only installation ? I've seen a document
( http://dev.eclipse.org/viewcvs/index.cgi/platform-update-hom e/doc/working/configuration-3.0.html?rev=1.2)
outlining changes - what has actually been implemented ?
I've found a developerWorks article by Pat Carthyon for v.2.1
( http://www-106.ibm.com/developerworks/opensource/library/os- ecfeat/) "Put
Eclipse features to work for you" - does the links dir method still apply
? Does the plugin_customization.ini method still apply for global
customizations ? (The Eclipse Project DRAFT 3.0 plan mentions "provide
user settings" for rich client platform - what has actually been done ?)
This is most likely a FAQ, but I write about this because I could not find
a clear answer in the midst of documents talking about "old ways" of doing
things and "planned" ways for 3.0.
Thanks for any pointers/help,
Regards,
Bernard
|
|
|
Powered by
FUDForum. Page generated in 0.02976 seconds
] 
Search
Help
Register
Login
Home
