Genuitec » All Posts Wed, 15 Aug 2018 10:27:27 +0000 en-US <![CDATA[Configuring the Network Proxy Settings]]> Fri, 20 Apr 2018 09:45:57 +0000 support-tony If your access to the Internet needs to go through a proxy server then eclipse needs to know about this in order to perform network related tasks. These tasks include installing or updating plugins and using tools that automatically download files from the Internet (such as maven and the Angular tooling). This information is only applicable if you need to access the Internet through a proxy.

For setups that have the proxy settings configured in the system (for example, in Windows via the Proxy page of system settings), then all that is needed is to set the Active Provider to “Native”, as shown in the following screenshot.

Native Setting

In this case, no other settings are needed.

If you don’t have a system proxy set but still need to go through a proxy, then set the Active provider to “Manual” and configure the appropriate schema in the “Proxy entries” section, as shown below.

Manual Setting

You should configure only the schema through which you connect to the proxy; it is not related to the URLs accessed through the proxy (for example, you can still access HTTPS URLs, through a proxy that you connect to with an HTTP URL, provided the proxy allows it). To configure a schema, select the line for that schema and click the “Edit” button then fill in appropriate entries as shown in this screenshot:

Edit Schema

Note that the name and password are only needed if you select the “Requires Authentication” option. In this case, see the note below.

If you have unneeded schema configured, select that schema line and click the “Clear” button.

Proxy Authentication

For JDK 8, update 111, a change was made to HTTPS tunneling for basic authentication which may cause your authentication to the proxy server fail (if it is needed), as per this release notice for that update which states:

In some environments, certain authentication schemes may be undesirable when proxying HTTPS. Accordingly, the Basic authentication scheme has been deactivated, by default, in the Oracle Java Runtime, by adding Basic to the jdk.http.auth.tunneling.disabledSchemes networking property. Now, proxies requiring Basic authentication when setting up a tunnel for HTTPS will no longer succeed by default. If required, this authentication scheme can be reactivated by removing Basic from the jdk.http.auth.tunneling.disabledSchemes networking property, or by setting a system property of the same name to “” ( empty ) on the command line.

Additionally, the jdk.http.auth.tunneling.disabledSchemes and jdk.http.auth.proxying.disabledSchemes networking properties, and system properties of the same name, can be used to disable other authentication schemes that may be active when setting up a tunnel for HTTPS, or proxying plain HTTP, respectively.

If this affects you, add the following lines to your eclipse.ini file (or equivalent, such as angularide.ini), somewhere after the -vmargs line:

]]> <![CDATA[Installing Webclipse Off-line]]> Tue, 31 Oct 2017 10:06:50 +0000 support-tony Although many Webclipse functions only make sense when connected to the internet (e.g. for downloading dependencies when creating new Angular projects), some users have asked about off-line installation.

We don’t have an archived update site or an installer for the Webclipse suite of tools but eclipse does offer a way to mirror update sites and this can be utilized to create an archived update site yourself. The instructions are given in this article but following is a summary, specific to Webclipse.

Check the update site for Webclipse by going to the Webclipse page in the eclipse MarketPlace and clicking the dowload icon, which will show the update site URL for supported eclipse releases. In the following commands, I’ll use the URL for eclipse Oxygen.

Now enter the following two commands, in succession, in a terminal or command prompt:

<eclipseFolder>/eclipse -nosplash -verbose -application org.eclipse.equinox.p2.metadata.repository.mirrorApplication -raw -source -destination <mirrorFolder>

<eclipseFolder>/eclipse -nosplash -verbose -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication -raw -source -destination <mirrorFolder>

Where <eclipseFolder>/ is the path to the folder containing the eclipse executable and <mirrorFolder> is the full path to the folder which is to contain the mirror.

You will see some information messages in the terminal window, many more for the second command but there should be no errors if you’ve entered the commands and paths correctly (note that Windows will have a different path separator character from Linux and Mac systems; the example above shows the Linux style for the eclipse folder path). At this point, you’ll have a local update site. You can compress this (or not) and copy it to another machine for off-line installation of Webclipse.

Let us know, on the regular forums, if you have any problems with this method.