|
|
Re: Profile folder name generation / Oomph RSE pre-config [message #1858409 is a reply to message #1858325] |
Sat, 01 April 2023 15:15 |
Mark Lawrence Messages: 28 Registered: February 2023 |
Junior Member |
|
|
Thank you for the pointers Ed!
I've had a look at the source and it appears to be the freeze() function in rse/plugins/org.eclipse.rse.core/src/org/eclipse/rse/internal/persistence/PropertyFileProvider.java responsible for appending this value. Transforms an arbitrary name into one that can be used in any file system that supports long names. The transformation appends a number to the name that captures the case of the letters in the name. If a character falls outside the range of understood characters, it is converted to its hexadecimal unicode equivalent. Spaces are converted to underscores.
I don't think it does, but unless Oomph has a way of running a small amount of custom Java code during installation (i.e. a copy of the freeze() code which takes its input from an oomph variable containing the machine hostname), I don't think its going to be possible to pre-define remote hosts connections in RSE via Oomph.
[Updated on: Sat, 01 April 2023 15:17] Report message to a moderator
|
|
|
|
|
|
Re: Profile folder name generation / Oomph RSE pre-config [message #1858440 is a reply to message #1858424] |
Mon, 03 April 2023 10:16 |
Mark Lawrence Messages: 28 Registered: February 2023 |
Junior Member |
|
|
I'm having a bit of trouble testing this, I'm using the following repo to source org.eclipse.oomph.setup (1.28.0.v20230402-0730 installs):
https://download.eclipse.org/oomph/drops/nightly/N20230402-230023/
...and I'm trying to create a resource at:
${workspace.location|uri}/.metadata/.plugins/org.eclipse.rse.core/profiles/PRF.${user.host.name|rseFreeze}/H.plex2_30/node.properties
...but it appears rseFreeze doesn't exist as its creating a folder with upper case & no appended _xxx. I have tried all of the nightly builds available. Am I doing everything correctly?
Another issue, our Oomph provides three products, which are essentially the same IDE but at different Eclipse versions (Neon, Photon, and 4.23). If this does work, I think its only going to work on 4.23, as oomph has a dependency on a given eclipse runtime version. Is there any way of back porting this filter so it can work on the oomph version used for Neon & Photon (oomph setup 1.23)?
[Updated on: Mon, 03 April 2023 10:53] Report message to a moderator
|
|
|
|
Re: Profile folder name generation / Oomph RSE pre-config [message #1858452 is a reply to message #1858446] |
Mon, 03 April 2023 15:58 |
Mark Lawrence Messages: 28 Registered: February 2023 |
Junior Member |
|
|
Sorry Ed, it makes sense now that its available in the installer!
Further troubles though, it seems Java 17 gives me a few problems using some of our update sites which I don't see when using Java 11:
ERROR: org.eclipse.equinox.p2.transport.ecf code=1002 Unable to read repository at https://<a server I dont own>/content.xml.
javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Any known way around this? Is the next Eclipse Installer fully moving to Java 17, with no Java 11 version?
[Updated on: Mon, 03 April 2023 16:13] Report message to a moderator
|
|
|
|
|
|
Re: Profile folder name generation / Oomph RSE pre-config [message #1858463 is a reply to message #1858462] |
Tue, 04 April 2023 09:31 |
Mark Lawrence Messages: 28 Registered: February 2023 |
Junior Member |
|
|
I'm reverting back to adding the certs to the keystore in order to test rseFreeze, however another issue I'm now seeing is I have a company internal update site I'm using which is http in my oomph config, however the installer seems to be converting it to https, so I get:
ERROR: org.eclipse.equinox.p2.transport.ecf code=1002 Unable to connect to repository https://<internal update site server>/IESRepos/4.8.0.Globalization/M20220325-0503/all/content.xml
org.apache.hc.client5.http.HttpHostConnectException: Connect to https://<internal update site server>:443 [<internal update site server>] failed: Connection refused
[Updated on: Tue, 04 April 2023 09:32] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04877 seconds