Details
-
Suggestion
-
Resolution: Timed out
-
None
-
0
-
Description
Right now only explicit project dependencies are picked up by Maven2 dependency analyzer.
In fact, a project is also implicitly dependent on it's immediate parent projects and all maven plugins that are required to build it. If any of those artifacts is provided by build plans deployed to the same Bamboo instance (which is almost always the case with parent project) a dependency relationship between the plans should be established.
The list of plugin artifacts needed for the build is readily available in Maven2 model classes. Please refer to maven-dependency-plugin dependency:resolve-plugins for an example.
As a workaround, one can add both parent project (using dependency type pom) and required plugins (using depdendency type maven-plugin) as explicit dependencies of the project. Then, Bamboo's dependency analyzer picks them up correctly. However it adds a bit of maintenance burden that could be easily eliminated.
Attachments
Issue Links
- is duplicated by
-
BAM-5318 Maven dependencies should take into account parent poms
- Gathering Interest