Jeff has pointed out that the names
for the proxy plug-ins are in a namespace that does not belong to the Platform
(i.e. org.eclipse.net) and that it is not clear that approval for getting
the name space would (or should) be granted by the Foundation (e.g. what
if a project named Net came along at some future time). Eclipse already
has a project dealing with communications (e.g. ECF) and it is easy to
argue that it makes sense to use that namespace for these projects as well
(e.g. org.eclipse.ecf.proxy and org.eclipse.ecf.proxy.ui).
The main issue with this is that the
plug-ins are being consumed by the Platform but would be in the namespace
of another project. A related issue is whether these projects would be
hosted in the repository of ECF or the Platform repository. The later would
be easier from a logistics standpoint for building the Platform but would
be confusing for product developers when trying to download the plug-ins
separately or check them out from the repository. However, if the projects
were hosted in the ECF project, we would need to come up with the process
for including the plug-ins in the SDK as we have no other instances of
We have not approached anyone on the
ECF project about tis yet as we would like to know what the PMC thins about
this before proceeding. I we feel this is the right direction, we can consult
with Scott to see what he thinks.
Michael Valenta/Ottawa/IBM@IBMCA Sent by: eclipse-pmc-bounces@xxxxxxxxxxx
20/02/2007 03:20 PM
Please respond to
[eclipse-pmc] Request for API additions
for Platform Level Proxy Settings and
I would like to request the addition of API to support the following two
bugs. In both cases the projects already exist in the repository so this
request is to add them to the build.
Platform Level Proxy Support - https://bugs.eclipse.org/bugs/show_bug.cgi?id=154100
This feature has been requested by WTP and other clients in order to reduce
the number of proxy preference pages (there were 3 in Callisto). For this
feature we have created two new projects: org.eclipse.net.core and org.eclipse.net.ui.
The Core plug-in consists of API to access and modify proxy settings
for HTTP, HTTPS and SOCKS proxies. There is also API for setting the non-proxied
hosts lists and API for allowing clients to retrieve proxy data by host.
The UI plug-in has API for setting the default Java Authenticator
Separate JSch preference pages from CVS - https://bugs.eclipse.org/bugs/show_bug.cgi?id=170883
This feature was requested by DSDP since they use JSch for SSH2 connections.
We would like to add two new projects: org.eclipse.jsch.core and org.eclipse.jsch.ui.
The Core plug-in consists of API to create a JSch Session that uses the
proper prefereces. The UI plug-in consists of API that provides basic password
- The new plug-ins push down Proxy and SSH2 preferences so that clients
do not need their own preference pages which leads to a better user experience.
There is minimal risk as the features focus on what is required for pushing
the preference pages down.
- should not have an impact
eclipse-pmc mailing list