Menu ▾ ▴

#168 Offer alternative p2 site than https://sourceforge.net/projects/eclipse-cs/files/updatesite/

Future
closed
Lars Koedderitzsch
None
1
2017-03-14
2017-01-31
Michael Vorburger
No

Lars,

A number of users of my https://github.com/vorburger/opendaylight-eclipse-setup, people who normally know what they are doing, regularly report recurring issues like item #7. on https://github.com/vorburger/opendaylight-eclipse-setup/blob/master/README.adoc#faq - somehow, the p2 in Oomph seems to struggle, for some reason, only for some users, with fetching eclipse-cs from https://sourceforge.net/projects/eclipse-cs/files/updatesite/ (via http://eclipse-cs.sourceforge.net/update/ ... I can't point it directly to https://sourceforge.net/projects/eclipse-cs/files/updatesite/ now, can I?). I was never able to locally repro. it, but it has come up often enough over the past 9 months or so that I suspect there is something.

I was wondering if perhaps this could be related to some weird combination of... something, and sourceforge.net hosting ... I mean it does work for me, but perhaps the HTML directory listing page is somehow interferring, for some?

Long story short - would you possibly consider and be willing to offer an alternative p2 site??

In my experience, a github.com gh-pages like repo works great! They do CDN and all for you - all free.

Could create a mirror myself, but seems a shame, thought I'd first ask you here.

Potentially willing to lend a hand, if you would like ...

M.

Discussion

  • Michael Vorburger

    Michael Vorburger - 2017-01-31

    Lars, an end user I was supporting has just identified what may be the root cause of problems some people seem to be having with p2 sites hosted on sourceforge.net .. there could be some issue with their SSL, which depending on Java version (Oracle Java vs. OpenJDK and exact OS and patches etc.) has impacts; for this user had this problem on an older OS (CentOS 6.4) whereas this wget worked for me...

    Of course a Java-based p2 installer (Oomph) isn't the same as wget, but still, I think this proves that hosting p2 update sites (only) on sourceforge.net project files can cause issues (I'm reasonably sure that what's shown below likely is the issue that some people hit with Oomph when using opendaylight-eclipse-setup; even if it's error message may not show that as clearly.)

    wget sourceforge.net/projects/eclipse-cs/files/updatesite/7.3.0/content.xml.xz
    --2017-01-31 17:16:02-- http://sourceforge.net/projects/eclipse-cs/files/updatesite/7.3.0/content.xml.xz
    Resolving sourceforge.net... 216.34.181.60
    Connecting to sourceforge.net|216.34.181.60|:80... connected.
    HTTP request sent, awaiting response... 301 Moved Permanently
    Location: https://sourceforge.net/projects/eclipse-cs/files/updatesite/7.3.0/content.xml.xz [following]
    --2017-01-31 17:16:02-- https://sourceforge.net/projects/eclipse-cs/files/updatesite/7.3.0/content.xml.xz
    Connecting to sourceforge.net|216.34.181.60|:443... connected.
    ERROR: certificate common name *.sourceforge.net' doesn't match requested host namesourceforge.net'.
    To connect to sourceforge.net insecurely, use `--no-check-certificate'.

     

  • Michael Vorburger

    Michael Vorburger - 2017-02-13

    We have had at least one user confirm that he has this special issue when running his Eclipse Installer under Oracle's JDK, but it went away when using OpenJDK! We believe that they have different root certificates, explaining this. Something seems to be particular with the SSL cert on https://sourceforge.net ...

     

  • Lars Koedderitzsch

    Lars Koedderitzsch - 2017-03-10

    Hi Michael,
    I've moved hosting of the update site to Bintray.com. The update site url remains unchanged.
    I hope this will resolve installation issues for the time being.

    Sorry for the long wait.

     

  • Lars Koedderitzsch

    Lars Koedderitzsch - 2017-03-10
    • status: open --> closed
     

  • Michael Vorburger

    Michael Vorburger - 2017-03-14

    Thank You!

     

Log in to post a comment.