Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-13142

Camel may package artifacts from different version

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.23.1
    • Fix Version/s: 3.0.0-M1, 3.0.0
    • Component/s: build system
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      When switching from one branch to another there is a (likely) possibility that component directories that existed in a previous checkout branch are no longer available in the current checkout branch. However, `camel-foo/target` with all the previously generated artifacts is still on the file system and cannot be detected by `git status` either. Neither will these stale target directories be removed by `mvn clean`.

      The camel packager plugin seems to be walking the camel directory structure and will package everything it finds. As a result the camel-2.23.2-SNAPSHOT catalog may contain a catalog entry that points to camel-browse-3.0.0-SNAPSHOT.

      As a workaround, I suggest to do something like this

      find . -type d -name target | xargs rm -rf
      

      before doing a clean mvn build.

      As a possible solution, it may be necessary for the thing that walks the directory structure to require at least one file that is maintained in SCM (e.g. pom.xml)

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              tdiesler Thomas Diesler
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: