Eclipse Community Forums: Oomph » Updating Eclipse.ini for default Eclipse Installer

Home » Eclipse Projects » Oomph » Updating Eclipse.ini for default Eclipse Installer

Updating Eclipse.ini for default Eclipse Installer [message #1783413]

Mon, 12 March 2018 14:57

Eclipse User

I'm internalizing the Eclipse installer, I have it working for basic stuff 100% internally.

However when I look at the launched version of Eclipse, the Update URL is still listed as the eclipse.org location.

Checking eclipse.ini file:

-Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
-Doomph.redirection.index.redirection=index:/->file:////c:/oomph-testing/org.eclipse.oomph.git/org.eclipse.oomph/setups/
-Doomph.redirection.index.location.redirection=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->archive:http://www.eclipse.org/setups/setups.zip!/http/git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/

How would I update that so the default "Simple Setup" for Eclipse for Java uses the proper setup paths. I have looked at "setups/org.eclipse.products.setup" and do not see where the ini would be updated.

Examples online do not see to show this either. I may be missing something obvious.

Re: Updating Eclipse.ini for default Eclipse Installer [message #1783438 is a reply to message #1783413]

Tue, 13 March 2018 03:40

Eclipse User

The things you show in the eclipse.ini appear to come from org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.addBootstrapTasks(EList<SetupTask>). The value for -Doomph.update.url= should be the value of that very same system property.

Re: Updating Eclipse.ini for default Eclipse Installer [message #1783640 is a reply to message #1783438]

Wed, 14 March 2018 15:55

Eclipse User

If I have taken a copy of the GIT site for Eclipse as I have, which file would I edit to change the eclipse.ini file.

I have setups/interms/Platform.setup which appears to set the URL's in question. This is under the "Master" area but I can't find where the actual file is.

How would I get the Master to edit locally. I understand its a stream but I can't seem to find documents on where this is stored locally.

Re: Updating Eclipse.ini for default Eclipse Installer [message #1783649 is a reply to message #1783640]

Thu, 15 March 2018 01:25

Eclipse User

In terms of a copy the GIT site, you're meaning the whole setups folder? How is the Platform.setup related to your question about the contents of the eclipse.ini?

Note that you can define Eclipse Ini tasks to change the contents of the eclipse.ini, but much of what's in that file is defined by p2 touchpoint actions in the p2 update sites and by basic p2 director implementation behavior, so you will not find a single fine that defines all the contents of the product's eclipse.ini. I've already mentioned that some tasks (the ones that concerned you) come logic in the code, i., org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.addBootstrapTasks(EList<SetupTask>), in particular a bunch of Eclipse Ini tasks; you could override any of those in your product setup.

Re: Updating Eclipse.ini for default Eclipse Installer [message #1784137 is a reply to message #1783649]

Thu, 22 March 2018 14:45

Eclipse User

Ed -
Is there a recommended path showing how to launch a custom version of the launcher,
I currently have the following which is working, but it still picking up a Previously Set setup index. I can't tell where this is being pulled from and I've already deleted C:\users\%username%\.eclipse and C:\users\%username\.p2 during testing.

set JAVA="C:\Program Files\Java\jdk1.8.0_141\bin\java.exe"
set LAUNCHER=c:\test\plugins\org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
set LAUNCHER_LIB=c:\test\plugins\org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.551.v20171108-1834\eclipse_1630.dll 
set UPDATE_URL=file://C:\mirror_test\org.eclipse.oomph\
set SETUPS_REDIRECT=index:/->file://C:\oomph_testing\oomphtesting\
set OUSER_HOME=file://C:\users\%userhome%\oomphtesting\ 

call %JAVA% -jar %LAUNCHER% -os win32 -ws win32 -arch x86_64 -showsplash --launcher.library %LAUNCHER_LIB% -startup %LAUNCHER% -Doomph.redirection.setups=%SETUPS_REDIRECT% -Doomph.installer.update.url=%UPDATE_URL% -Doomph.setup.ecf.trace -Duser.home=%OUSER_HOME% -Doomph.setup.user.home.redirect=true -consoleLog

Edit:

Figured this out, as it a bit of a Caching circle that may need to be documented somewhere more obvious,

in the exploded Eclipse Installer there is a file called configuration\org.eclipse.oomph.setup\indicies.xmi

<?xml version="1.0" encoding="UTF-8"?>
<base:Annotation
    xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:base="http://www.eclipse.org/oomph/base/1.0"
    source="IndexLocations">
  <detail key="file://C:\oomph_testing\oomphtesting\org.eclipse.setup">
    <value>Eclipse</value>
  </detail>
  <detail key="archive:http://www.eclipse.org/setups/setups.zip!/http/git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/org.eclipse.setup">
    <value>Eclipse</value>
  </detail>
</base:Annotation>

Deleting this file means it now looks for the -Doomph.redirection.setups=%SETUPS_REDIRECT% but it can't seem to find it, which is confusing me. Logs show it trying to access the github location still, and erroring out with a Proxy error in the Eclipse Installer.

[Updated on: Thu, 22 March 2018 16:31] by Moderator

Re: Updating Eclipse.ini for default Eclipse Installer [message #1784173 is a reply to message #1784137]

Fri, 23 March 2018 04:39

Eclipse User

It's probably generally a good idea to test whatever you are doing with VM arguments in an Oomph development environment's launcher first where you can set a breakpoint in ECFURIHandlerImpl. Then you can see what is being accessed and that makes it more likely you can understand why it is being accessed, i.e., from the call stack it's likely more clear. You show stuff above, but you should note that there is nothing special about the Doomph.redirection.setups variable name, other than that is is a variable that will be used to do redirection. Given I don't know the value of %SETUPS_REDIRECT% I can't know what you've actually done. Also, have you done anything to redirect the setup archive itself?

public static final URI INDEX_SETUP_ARCHIVE_LOCATION_URI = URI.createURI("http://www.eclipse.org/setups/setups.zip");

I.e., have you used the SetupArchiver application to create an archive of your specialized index?

Re: Updating Eclipse.ini for default Eclipse Installer [message #1784230 is a reply to message #1784173]

Fri, 23 March 2018 16:47

Eclipse User

I have everything in the initial area working now Ed, thanks.

This forum entry at https://www.eclipse.org/forums/index.php?t=msg&th=1091330&goto=1781414&#msg_1781414 helped a lot and also re-watched your 1.5 hour Eclipse Youtube video

Issue turned out to be caused by some stupid mistakes caused by Whitespace and an extra command option added on the same line I missed.

Yes, dumb sorry.

Re: Updating Eclipse.ini for default Eclipse Installer [message #1784239 is a reply to message #1784230]

Sat, 24 March 2018 04:51

Eclipse User

Big glaring errors attract attention, but he smallest/simplest problems are often the hardest to spot.

Re: Updating Eclipse.ini for default Eclipse Installer [message #1784320 is a reply to message #1784239]

Mon, 26 March 2018 14:05

Eclipse User

Ed, shouldn't this redirect the location to get the Eclipse Install when put into the Eclipse.ini file? when doing the install this is still grabbing them from download.eclipse.org location. I know you can't redirect P2 directly, but other forum posts make it seem possible.

-Doomph.redirection.oxygen=http://download.eclipse.org/releases/oxygen/->//myshare/path/to/download.eclipse.org/releases/oxygen/

When I get to the Bootstrapping Tasks it is not listed there.

Edit: I added the Oxygen-Epp redirection and that one is appearing and showing up, not on the BootStratp section but during the actual install. I'll re-download the Oxygen Repository and Meta Data to make sure there isn't an corruption causing it to not be seen as valid. Even though the repository can be used to update and install new plug-ins.

[Updated on: Mon, 26 March 2018 16:35] by Moderator

Re: Updating Eclipse.ini for default Eclipse Installer [message #1784334 is a reply to message #1784320]

Mon, 26 March 2018 21:03

Eclipse User

A -D option is not a task, and -Doomph.redirection.* variables are used to help redirect the setup files themselves. There is a Redirection task you can use to redirect URIs used in tasks. Note that if the http://download.eclipse.org/releases/oxygen is used directly in a task, then redirecting http://download.eclipse.org/releases/oxygen/ will not redirect it but only URI nested under it. Note also that update sites can include references to other update sites, so you should check that your mirrored site doesn't do that...

Re: Updating Eclipse.ini for default Eclipse Installer [message #1784337 is a reply to message #1784334]

Mon, 26 March 2018 23:11

Eclipse User

Thanks Ed,

I sterilize our p2 data so that the external references are repointed, as you say there are cases where the Artifact.(jar,xml) file points to an external site making the local mirror redundant.

I've re-mirrored the site and confirmed the files are all pointing locally. It works for the Oxygen-Epp section but not the original Oxygen which is interesting. I'll have to look at the task.

I was trying to see how much I could get away using a "Pure" mirror of the Github for the setup files to cut down on future management but this may be just adding to much to my troubles as it is.

Thanks for the pointers.

Previous Topic:	[NEED HELP] An internal error occurred during: "JavaEditorMessages.SemanticHighlighting_job&quo
Next Topic:	Subproject selection behaviour

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 20 02:57:36 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter