Menu

#1271 Check for Updates fails - pmd-eclipse/update-site/content.xml not available

Eclipse-Plugin
obsolete
None
PMD
3-Major
Bug
2016-10-01
2014-10-16
gho
No

"Eclipse -> Check for Updates" reports
"Unable to read repository at https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/content.xml."

Discussion

  • Andreas Dangel

    Andreas Dangel - 2014-10-24

    That's correct - a content.xml file doesn't exist. The file is called content.jar.

    Can you verify, that you have the following URL configured for the repository in eclipse?

    https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/

    If it still doesn't work, please post the eclipse version, you are using.

     
  • gho

    gho - 2014-10-28

    Eclipse version is Luna. May be problem had to do with bad proxy settings.

     
  • Andreas Dangel

    Andreas Dangel - 2014-11-15
    • status: open --> obsolete
    • assigned_to: Andreas Dangel
    • Milestone: New Tickets --> Eclipse-Plugin
     
  • Andreas Dangel

    Andreas Dangel - 2014-11-15

    I assume this is fixed now. Closing this ticket.

     
  • lupulcelbun

    lupulcelbun - 2015-03-31

    Install and upgrade issue is still present in Luna.

     
  • lupulcelbun

    lupulcelbun - 2015-03-31

    What is interesting that it seems to work after a while.
    Why does it look for content.xml if no such file exists?

     
  • Charles

    Charles - 2016-09-30

    Hi,
    I am using STS 3.7.2.RELEASE (tried Juno Service Release 2 also).
    When I tried to install PMD bellow expetion is show.
    Unable to read repository at https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/content.xml.
    sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    Please help me on this.

     
  • Andreas Dangel

    Andreas Dangel - 2016-10-01

    Linking to the new bug [#1528] in case someone ends up here.

     

    Related

    Issues: #1528


Log in to post a comment.

MongoDB Logo MongoDB