How to fix error “Updating Maven Project”. Unsupported IClasspathEntry kind=4?

前端 未结 15 1696
自闭症患者
自闭症患者 2020-12-02 03:44

I have imported maven project in STS, when I run update update project I receive:

\"Updating Maven Project\". Unsupported IClasspathEntry kind=4
相关标签:
15条回答
  • 2020-12-02 04:00

    Upgrading from Kepler to Luna worked for me.

    I had just added some components for Java 1.8 support. It seems that they where not as compatible as I would like or that I mixed the wrong ones. It really caused a lot of problems. Trying to update the system reported errors as they couldn't fulfill some dependencies. Maven upgrades didn't work. Tried a lot of things.

    So, if there is no reason to avoid the upgrade just add the luna repository to avalilable software sites (Luna http://download.eclipse.org/releases/luna/ ) and "check for updates". It is better to have all the components with the same version and there are some nice new features.

    0 讨论(0)
  • 2020-12-02 04:03

    Try mvn clean install eclipse:eclipse -Dwtpversion=2.0 command on DOS command prompt. Suggesting you because , It worked for me!!

    0 讨论(0)
  • 2020-12-02 04:10

    This error is also thrown if the update command is used on a project instrumented for code coverage with Clover.

    To resolve in this scenario: Un-instrument the project folders you wish to update. Run the maven update then instrument for code coverage again.

    0 讨论(0)
  • 2020-12-02 04:11

    Have you tried:

    1. If you have import project into the eclipse 4, please delete it.
    2. In maven consol, run: mvn eclipse:clean
    3. In Eclipse 4: File -> Import -> Maven -> Existing Maven Projects
    0 讨论(0)
  • 2020-12-02 04:11

    Seeing all other answers. I found for me a simpler way.

    I just removed all lines in the .classpath (editing with eclipse) containing a var and used maven -> update project without an error.

    0 讨论(0)
  • 2020-12-02 04:11

    I'm using Eclipse 4.3.2 (Kepler) with M2E 1.4.x and felt over this problem several times!

    In my case the "mvn eclipse:eclipse" command also generates Checkstyle, PMD and Findbugs configuration so "mvn eclipse:clean" does not help me because it drops all those config files again.

    The best solution for me was to delete all ".classpath" files:

    find . -name ".classpath" -delete
    

    and import the project into eclipse afterwards.

    0 讨论(0)
提交回复
热议问题