Results 1 to 6 of 6

Thread: Problem indexing central maven repository

  1. #1
    Join Date
    Aug 2010
    Location
    Ottawa, Canada
    Posts
    53

    Angry Problem indexing central maven repository

    Hi,

    I just created a fresh new workspace (hence a brand new .metadata\.plugins\org.eclipse.m2e.core\nexus subfolder), then opened the maven repositories view and right click the global central repository and select rebuild index. All I get in the Eclipse error log is the following (with no stack trace, grrr):

    eclipse.buildId=2.9.0.201203011000-RELEASE
    java.version=1.6.0_24
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA
    Framework arguments: -product com.springsource.sts.ide -showlocation
    Command-line arguments: -os win32 -ws win32 -arch x86 -product com.springsource.sts.ide -showlocation

    Error
    Fri Mar 30 11:56:06 EDT 2012
    Unable to update index for central|http://repo1.maven.org/maven2

    I know that the General/Network Connection proxies settings are correct and that the ~/.m2/settings.xml proxy settings are also correct. However, no cigar. Can anyone shed some light or provide a fix/workaround?
    Mario Jauvin

  2. #2
    Join Date
    Sep 2008
    Location
    Hamburg, Germany
    Posts
    1,637

    Default

    Hey Mario!

    Is this a temporary problem with accessing updating the maven index or do you see this error with every Eclipse/STS installation on your machine?

    Cheers,
    -Martin
    Martin Lippert
    SpringSource, a division of VMware
    SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/martinlippert

  3. #3
    Join Date
    Aug 2010
    Location
    Ottawa, Canada
    Posts
    53

    Default

    I only have one installation of STS 2.9.0 on my system and I see this all the time. Is there some debugging or tracing I could turn on to get more information?
    Mario Jauvin

  4. #4
    Join Date
    Sep 2008
    Location
    Hamburg, Germany
    Posts
    1,637

    Default

    Hey!

    Did you try maybe this:
    http://www.svlada.com/blog/2011/09/2...ven-orgmaven2/

    (with org.eclipse.m2e.core instead of org.maven.ide.eclipse)

    -Martin
    Martin Lippert
    SpringSource, a division of VMware
    SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/martinlippert

  5. #5
    Join Date
    Aug 2010
    Location
    Ottawa, Canada
    Posts
    53

    Default

    I found out the problem. The http proxy is at cause. Is there additional tracing that can be added so this can be identified faster in the future? Thanks
    Mario Jauvin

  6. #6

    Default

    I had this problem with STS 2.8.2, upgrading to STS 2.9.2 solved it-

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •