zDev - M2E - WTP OSS
  1. zDev - M2E - WTP OSS
  2. MECLIPSEWTP-40

Having "Build Automatically" set on eclipse workspace creates never ending loop of building when nothing has actually changed.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Out of scope
    • Affects Version/s: None
    • Fix Version/s: 0.13.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      Eclipse 3.5 (Galileo) Build id: 20090920-1017
      M2Eclipse 0.9.9.200911171109
    • Global Rank:
      12875

      Description

      When the build automatically option is enabled within eclipse, it seems that eclipse goes into this endless cycle of building all of the projects for no apparent reason when nothing has changed.

      I am using m2eclipse with web tools and i can see that when running my eclipse managed instance of tomcat that my web application is constantly re-deploying itself. I can also see that when it does actually deploy and begins the initialize the web application all of the resources are missing, so the build would appear to be only partially complete when tomcat attempts to hot-deploy any workspace changes, or at the very least another build has started and the resources have been removed as part of the build process.

        Activity

        Hide
        Kenneth DeLong added a comment -

        When we use this settings file, we experience the infinite build loop. If we use a "stock" settings.xml, the build loop disappears.

        Show
        Kenneth DeLong added a comment - When we use this settings file, we experience the infinite build loop. If we use a "stock" settings.xml, the build loop disappears.
        Hide
        Kenneth DeLong added a comment -

        This bug http://jira.codehaus.org/browse/WAGON-73 seems to indicate that the problem was fixed in wagon 1.0-beta-3. However, when I run my build (after cleaning out the wagon dir in my local repo), I see 1.0-alpha-6 and 1.0-beta-2 being brought down. I've updated the versions of all the plugins to the lastest in my POM, I've sent dependencyManagement to 1.0-beta-6 for wagon, used Maven 3 with and without my company parent pom, but those two old versions of wagon are the only ones that get brought down. Is there any way to find out what it is that is bringing wagon into my build, and force it to use the later version?

        Show
        Kenneth DeLong added a comment - This bug http://jira.codehaus.org/browse/WAGON-73 seems to indicate that the problem was fixed in wagon 1.0-beta-3. However, when I run my build (after cleaning out the wagon dir in my local repo), I see 1.0-alpha-6 and 1.0-beta-2 being brought down. I've updated the versions of all the plugins to the lastest in my POM, I've sent dependencyManagement to 1.0-beta-6 for wagon, used Maven 3 with and without my company parent pom, but those two old versions of wagon are the only ones that get brought down. Is there any way to find out what it is that is bringing wagon into my build, and force it to use the later version?
        Hide
        Igor Fedorenko added a comment -
        Show
        Igor Fedorenko added a comment - You can try recent 0.12.0 SNAPSHOT build from https://repository.sonatype.org/content/repositories/forge-sites/m2e/0.12.0/N/0.12.0.201010142002/
        Hide
        Kenneth DeLong added a comment -

        Has anything in the 0.12 version to address this bug?

        Show
        Kenneth DeLong added a comment - Has anything in the 0.12 version to address this bug?
        Hide
        Fred Bricon added a comment -

        I believe this is an upstream issue that has been fixed with the new lifecycle mapping architecture in m2e-core 1.0.0

        Please re-open if you're still seeing this issue with m2e 1.0.0 and m2e-wtp 0.13.0

        Show
        Fred Bricon added a comment - I believe this is an upstream issue that has been fixed with the new lifecycle mapping architecture in m2e-core 1.0.0 Please re-open if you're still seeing this issue with m2e 1.0.0 and m2e-wtp 0.13.0

          People

          • Assignee:
            Unassigned
            Reporter:
            Mark A. Kobold
          • Votes:
            18 Vote for this issue
            Watchers:
            16 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Date of First Response: