maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <>
Subject [jira] (MPIR-269) (optionally) create dependency convergence also for single module projects
Date Tue, 02 Apr 2013 10:40:52 GMT


Olivier Lamy commented on MPIR-269:

"Generates the Dependency Convergence report for reactor builds."

@Steven :P 

> (optionally) create dependency convergence also for single module projects
> --------------------------------------------------------------------------
>                 Key: MPIR-269
>                 URL:
>             Project: Maven 2.x Project Info Reports Plugin
>          Issue Type: Improvement
>          Components: dependency-convergence
>    Affects Versions: 2.6
>            Reporter: Michael Wenig
> 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)?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message