Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-19464

m2e-apt doesnt delete old build path

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.3.1.CR1
    • 4.3.0.Alpha1
    • maven, upstream
    • None
    • Hide

      I cant reproduce this 100%, but it happened to me 4-5 times. The best steps I have are here:
      1. Create maven project, add hibernate-jpamodelgen dependency and maven-processor-plugin
      2. Set project's maven annotation processing strategy to experimental
      3. Let the project update
      ASSERT: target/generated-sources/apt was added to build path
      4. delete maven-processor-plugin
      5. change project's maven annotation processing strategy to JDT, update project
      FAIL (sometimes..): build path contains both target/generated-sources/apt and target/generated-sources/annotations

      Show
      I cant reproduce this 100%, but it happened to me 4-5 times. The best steps I have are here: 1. Create maven project, add hibernate-jpamodelgen dependency and maven-processor-plugin 2. Set project's maven annotation processing strategy to experimental 3. Let the project update ASSERT: target/generated-sources/apt was added to build path 4. delete maven-processor-plugin 5. change project's maven annotation processing strategy to JDT, update project FAIL (sometimes..): build path contains both target/generated-sources/apt and target/generated-sources/annotations

      m2e-apt sometimes doesnt delete old build path resulting in having two (or more) same classes in build path. See attached screenshot.

        1. apt.png
          apt.png
          44 kB
        2. test-buildpath.zip
          3 kB

              fbricon@redhat.com Fred Bricon
              rawagner@redhat.com Rastislav Wagner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: