Re: Augment pom dependencies information with custom ones

On 12/5/19 6:56 PM, Francois MAROT wrote: > I have to generate a report listing all my dependencies (and I have tooo > many !) and for each one I have to provide a little text telling why I chose > this library. This was discussed a long time ago, see

Re: Augment pom dependencies information with custom ones

Hi François, If you have control over report generation, what you can do is add xml processing instructions into your pom files that your plugin can later parse out of the xml without interfering with existing pom model. M2Eclipse uses that approach to add some metadata to plugin executions.

Re: Augment pom dependencies information with custom ones

Hi François, I would start with the Dependency Analyze Report: http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html It offers valuable insight because it can often tell you whether your

Augment pom dependencies information with custom ones

Hello again (I'm active there today ;) ), this time I'd like to tell you about a feature I would like, and maybe some of you will have something to advise me. I have to generate a report listing all my dependencies (and I have tooo many !) and for each one I have to provide a little text

Ensure dependency convergence restricted to a given artifactId

Hello all, First of all thanks thanks and thanks again to the Maven devs, you rock ! Then a question: is there a way to limit the dependency convergence check (in Maven enforcer plugin - https://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html ) to a given artifactId (or a list