You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Steven Swor (JIRA)" <ji...@codehaus.org> on 2013/03/06 23:27:52 UTC

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

    [ https://jira.codehaus.org/browse/MPIR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321557#comment-321557 ] 

Steven Swor commented on MPIR-269:
----------------------------------

Agreed.  The "ready for release" info in this report is useful for single-module projects.

I just spent a good half hour trying to figure out why the report wouldn't run for my project, and ended up stepping through the code in a debugger until I found it.  If the behavior isn't going to be changed, can someone please at least update the documentation for this goal to mention that it "requires a reactor build" (or "only generates a report for multi-module projects")?
                
> (optionally) create dependency convergence also for single module projects
> --------------------------------------------------------------------------
>
>                 Key: MPIR-269
>                 URL: https://jira.codehaus.org/browse/MPIR-269
>             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: http://www.atlassian.com/software/jira