Eclipse Community Forums: Oomph » Basic Setup still Accessing outside world

Home » Eclipse Projects » Oomph » Basic Setup still Accessing outside world

Basic Setup still Accessing outside world [message #1791727]

Wed, 04 July 2018 09:42

Eclipse User

I have internalized the Eclipse Oomph install and this is working 100% in Advanced Mode.

In Basic Mode it is trying to reach out to external Eclipse.org mirrors. I cannot figure out why.

The Eclipse.ini are redirected properly internally.

-Doomph.redirection.archive=http://www.eclipse.org/setups/setups.zip-><internalURL>
-Doomph.redirection.setups=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/-><internalURL>
-Doomph.redirection.oomph=http://download.eclipse.org/oomph/products/repository-><internalURL>
-Doomph.update.url=<internalURL>

The only thing right now I can figure out is that Basic may read the setups.zip archive file differently than Advanced. Does this sound reasonable?

Re: Basic Setup still Accessing outside world [message #1791741 is a reply to message #1791727]

Wed, 04 July 2018 11:33

Eclipse User

Do you know the specific URL that's being accessed?

You might try setting a breakpoint in org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.createInputStream(URI, Map<?, ?>) because I'm pretty sure all internet traffic is funneled through that.

I think all the setups.zip processing is done with common code between the two modes because it's done in the core...

Re: Basic Setup still Accessing outside world [message #1791742 is a reply to message #1791741]

Wed, 04 July 2018 11:44

Eclipse User

This is where its getting strange. I thought I had figured it out, as being a reference from JBossTools to eclipse.org that I found in the Content.jar file. However after removing that and testing again it still happening.
I then realized that JBossTools isn't even referenced in the Oxygen Installer, its part of the Neon install option. So I will go line-by-line through the rules to see if I transposed some version number somewhere.

But thanks for the hint on the breakpoint location. Using that to test things

Re: Basic Setup still Accessing outside world [message #1791745 is a reply to message #1791742]

Wed, 04 July 2018 12:36

Eclipse User

Of course that was only a breakpoint for accessing setups. The p2 stuff is more complicated. A p2 repo can compose other repos but it can also have references to other repos, so if you mirror a repo, you'll end up with the same references as the original.

For p2 transport you could set a breakpoint in org.eclipse.oomph.p2.internal.core.CachingTransport.download(URI, OutputStream, long, IProgressMonitor)

Re: Basic Setup still Accessing outside world [message #1791887 is a reply to message #1791745]

Fri, 06 July 2018 10:01

Eclipse User

I've Audited every P2 Repository we have in-house. I've removed all reference to external sites.
What is confusing me here is that the ADVANCED install that uses the exact same model. However the Basic model is having errors accessing the other side, and it seems to be around JBossTools. JBossTools isn't even part of the Repo that is being referenced by the model. Its part of a repo for an earlier release of Eclipse.

I'm going through the Oomph models trying to figure out if there is a different set of models that are used in Basic installs vs Advanced installs? (Advanced mode works, Basic mode does't)

Re: Basic Setup still Accessing outside world [message #1791889 is a reply to message #1791887]

Fri, 06 July 2018 11:16

Eclipse User

No, both modes use the same underlying engine with the same model inputs. Are you able to run this is debug mode and set breakpoints on p2's transport layer to see the traffic? I wonder if possibly https://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/plugins/org.eclipse.oomph.p2.core/src/org/eclipse/oomph/p2/internal/core/ProfileImpl.java#n496 is adding a local repository that has a remote reference. Without being able to debug, this will be hard to figure out...

Re: Basic Setup still Accessing outside world [message #1791996 is a reply to message #1791889]

Mon, 09 July 2018 09:15

Eclipse User

Hi Ed,
It appears that in Basic Mode, the code you highlighted causes the Oomph launcher to try to load every repository listed, even if it is not part of the model. This doesn't appear to happen in Advanced mode.

I should mention this is the case of a Composite Archive/Content site where multiple Update Sites are kept in one file to make it easier for end users.

[Updated on: Mon, 09 July 2018 09:19] by Moderator

Previous Topic:	Path location to setup file
Next Topic:	headless oomph?

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 20 02:42:39 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter