Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-9342

Maven dependency task cannot handle Maven3 projects

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 4.3
    • 3.1, 3.2, 4.1.2, 4.2.1
    • Maven

      Bamboo embeds Maven 2.1.0 to read project metadata for the Automatic Dependency task. This version of Maven has problems reading POM and metadata files built with Maven 3.0.x.

      This change cannot be back ported to 3.2.x as changing the Maven version has certain risks attached to it that can only be mitigated by a full release of Bamboo by running through teams quality control process.

            [BAM-9342] Maven dependency task cannot handle Maven3 projects

            LucasA added a comment -

            LucasA added a comment - https://support.atlassian.com/browse/JST-51620

            it is also broken in Bamboo 4.0.1 (probably even 4.1 ?, so the "affects version" should be updated to reflect that

            Michael Häusler added a comment - it is also broken in Bamboo 4.0.1 (probably even 4.1 ?, so the "affects version" should be updated to reflect that

            +1 to John Petersam's comment.

            Raymond Smith added a comment - +1 to John Petersam's comment.

            I'd like to see the priority of this be bumped up. While we do have a workaround (manual dependency checking), it can become very ugly when you have a complicated heirarchy, and require multiple clones of projects to accomplish all of your tasks (i.e. build, site deploy, tag & branch building, etc.).

            John Petersam added a comment - I'd like to see the priority of this be bumped up. While we do have a workaround (manual dependency checking), it can become very ugly when you have a complicated heirarchy, and require multiple clones of projects to accomplish all of your tasks (i.e. build, site deploy, tag & branch building, etc.).

            rkrzewski added a comment -

            Updating to 2.2.1 is probably a good idea, considering that it contains important bug fixes over previous 2.x versions.
            My gut feeling however is that you'll need to embed both 2.2.1 and 3.0.x to support mixed M2 / M3 environments, and also provide separate Maven Dependency Processor tasks or a single task with configuration option for selecting Maven runtime, whichever is easier.

            rkrzewski added a comment - Updating to 2.2.1 is probably a good idea, considering that it contains important bug fixes over previous 2.x versions. My gut feeling however is that you'll need to embed both 2.2.1 and 3.0.x to support mixed M2 / M3 environments, and also provide separate Maven Dependency Processor tasks or a single task with configuration option for selecting Maven runtime, whichever is easier.

            Krystian, apparently >= 2.0.10 has some compatibility for Maven 3 produced metadata. Maybe we should upgrade to the latest 2.2.0 in Bamboo?

            James Dumay added a comment - Krystian, apparently >= 2.0.10 has some compatibility for Maven 3 produced metadata. Maybe we should upgrade to the latest 2.2.0 in Bamboo?

            MarkC added a comment -

            Mate how did this one go?

            MarkC added a comment - Mate how did this one go?

              asridhar AjayA
              kbrazulewicz Krystian Brazulewicz
              Affected customers:
              13 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: