| Oomph keep on adding site in available update sites [message #1748878] |
Tue, 29 November 2016 16:28  |
 Dominique Jean-Prost
Messages: 12
Registered: August 2016 |
Junior Member |
|
|
Hello,
After many tries, I finally managed to have an almost automatic eclipse installation for my whole team.
I defined a project setup, in which I require a bunch of eclipse plugins to be installed.
I do need the installer to use my nexus proxy, so that everyone doesn't download the whole internet on his side.
To be able to achieve this, I have to add 2 redirects entries in eclipse-inst.ini :
-Doomph.redirection.oomph=http://download.eclipse.org/oomph/updates/milestone/latest->http://cerbere:8081/nexus/content/repositories/oomph/
-Doomph.redirection.neon=http://download.eclipse.org/releases/neon/201606221000->http://cerbere:8081/nexus/content/repositories/eclipse-neon-update/
Eclipse installation goes well till the end by downloading everything needed through my nexus proxy. I added the different update site urls (from nexus) in the project.setup.
Now the problem :
Every time I launch Eclipse, it tries to apply setup, but it fails because the following available update sites are automatically added by I don't know what :
<bookmarks>
<site url="http://download.eclipse.org/releases/neon/201610111000" selected="true" name=""/>
<site url="http://download.eclipse.org/technology/epp/packages/neon" selected="true" name=""/>
</bookmarks>
As these update site are using direct access to the internet, and not my nexus proxy, it fails with this error :
ERROR: org.eclipse.equinox.p2.transport.ecf code=1002 HTTP Proxy Authentication Required: http://download.eclipse.org/releases/neon/201610111000/content.xml
ERROR: org.eclipse.ecf.identity code=0 Proxy Authentication Required
at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:291)
at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
How can I do to prevent these update sites to be added again and again ?
I tried to add a redirection in a setup task, it didn't change anything.
Thank you for helping.
dom
|
|
|
|
| Re: Oomph keep on adding site in available update sites [message #1748956 is a reply to message #1748917] |
Wed, 30 November 2016 12:52  |
Dominique Jean-Prost
Messages: 12
Registered: August 2016 |
Junior Member |
|
|
Hello Ed,
Well I'm not sure I understood correctly what you meant.
I understand that you say I should add redirections tasks in my project setup, so that these redirections would be used when eclipse tries to access the redirected update sites.
Actually, eclipse tries to access http://download.eclipse.org/releases/neon/201610111000 and http://download.eclipse.org/technology/epp/packages/neon when checking for updates, although I did not use them explicitly. With such redirections, it would do so by accessing the redirected urls, wouldn' it ?
If so, I will give a second try, as after so many tries, I'm not sure exactly of what I did.
Thank you.
dom
|
|
|
|
| Re: Oomph keep on adding site in available update sites [message #1750551 is a reply to message #1748878] |
Thu, 22 December 2016 13:55 |
Andrey Loskutov
Messages: 89
Registered: July 2009 |
Member |
|
|
I have also same issue if trying to use "default" Eclipse builds. They contain p2.inf files with p2 installation instructions like those:
instructions.configure=\
addRepository(type:0,location:http${#58}//download.eclipse.org/eclipse/updates/4.6,name:The Eclipse Project Updates);\
addRepository(type:1,location:http${#58}//download.eclipse.org/eclipse/updates/4.6,name:The Eclipse Project Updates);\
addRepository(type:0,location:http${#58}//download.eclipse.org/releases/neon,name:Neon);\
addRepository(type:1,location:http${#58}//download.eclipse.org/releases/neon,name:Neon);
Those instructions instruct Eclipse to add those update sites to the Eclipse on first startup, and you can't just disable it somehow (or I'm unaware about this).
So either your build your own package or (simpler) you have to patch the p2.inf files coming with your Eclipse flavour and remove those crazy instructions or (I haven't tested this) you add your own features with your p2.inf files which *remove* those update sites on first startup.
I've just removed those instructions and re-build SDK to get rid of it, but I've also interested in your experience.
|
|
|
|
| Re: Oomph keep on adding site in available update sites [message #1752456 is a reply to message #1752421] |
Tue, 24 January 2017 05:01 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
I'm not sure specifically what has worked for you and what hasn't. But note that p2 update sites are used in the installer itself so if you have an Eclipse Ini task, that will have no impact until the the installation that's been created is launched. To change which update sites are used in the installer, you'd have to edit the eclipse-inst.ini of the installer, or use a redirection task.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03276 seconds
] 
Search
Help
Register
Login
Home
