Results 1 to 5 of 5

Thread: Lifecycle mapping "org.eclipse.m2e.jdt.JarLifecycleMapping" is not available

  1. #1
    Join Date
    May 2006
    Location
    Madrid
    Posts
    382

    Default Lifecycle mapping "org.eclipse.m2e.jdt.JarLifecycleMapping" is not available

    Hello,

    I'm working with several projects and some of them doesn't compile with this error message that belongs to the pom.xml file:

    Lifecycle mapping "org.eclipse.m2e.jdt.JarLifecycleMapping" is not available. To enable full functionality, install the lifecycle mapping and run Maven->Update Project Configuration.
    In the overview tab of the pom.xml editor, I can click the error in order to tell STS to search for an appropriate connector. It works but it finds nothing.

    The weird thing is:

    * Some projects compiles one day, but the next day shows the error. If I delete the project, re-import it or even close the entire STS it compiles again.

    For instance, the Spring Integration samples that are available at github: /basic/file or /basic/helloworld

    * Other projects doesn't compile ever, but when I using maven from the console I see a BUILD SUCCESS.

    Does anybody else have the same problem?

    Regards.

  2. #2
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    747

    Default

    First, you should understand what the "Lifecycle mapping" problem is: http://wiki.eclipse.org/M2E_plugin_e...on_not_covered

    You may also want to read the STS FAQ on m2eclipse: http://forum.springsource.org/showth...for-STS-2-8-1)

    So, you can revert back to the older m2eclipse if you don't want to deal with lifecycle mappings, or you can mark the plugin's execution as being ignored inside of STS (there should be a quickfix for that).
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

  3. #3
    Join Date
    May 2006
    Location
    Madrid
    Posts
    382

    Default

    Thanks.

    I'm aware of these documents, but it's hard to find the concrete JarLifecycleMapping.

    My question was mainly about the weird fact with Spring Integration projects: sometimes compile, sometimes not.

    At the end I use maven from the console, and an old STS 2.7.1. I'd rather to downgrade the m2eclipse.

    But thanks for answering me (and I apologize for speaking like Tarzan)

  4. #4
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    747

    Default

    As the document mentions, it is possible to downgrade your m2eclipse from the STS dashboard. Open it up, click on the extensions tab and scroll down until you see m2eclipse v0.13. If you install that, it automatically uninstalls v1.0 of m2eclipse.
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

  5. #5
    Join Date
    May 2006
    Location
    Madrid
    Posts
    382

    Default

    Sorry, I meant I'd rather NOT to downgrade, because I have several versions of STS installed.

    But I was in a hurry and I couldn't review my post.

    I appreciate a lot the time that you've wasted with my issue and I'm so sorry for bothering you with my last comment.

    Greetings.

Posting Permissions

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