[MPIR-269] (optionally) create dependency convergence also for single module projects

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.6
• Component/s: dependency-convergence
• Assignee: Unassigned
• Reporter: Michael Wenig
• Created: 18/Jan/13 04:29
• Updated: 05/Jul/14 13:16
• Resolved: 05/Jul/14 13:16

Description

We are using the dependency convergence report for a quick check if a project could be released or not. Unfortunately the report is not created for single module projects.

MPIR-10 mentions that it is useful for multi module and therefore disabled by default for single module projects. Unfortunately "by default" is not correct as there is no option to activate it.

At our site the report also makes sense for single modules. The report shows if there are snapshot versions of other projects used.

Of course someone could take a look into the dependency report and search for SNAPSHOT. But it is a lot easier for the developers to follow a simple rule "look into this report" - and it could be used programmatically if the report is alway present.

Is there any reason against activating this report also for single module (an option which is false per default would be sufficient)?

Issue Links

• duplicates: MPIR-295 Enhancements on dependency convergence report