Hi Jason, That should be fine, I wrote it with that kind of separation in mind. The class file analyser is totally independent of Maven, so not sure whether that would move it out of maven-shared and into plexus-components? It's only the mojo that brings in the Maven dependencies - any preference to where that should live too?
Cheers, Mark Shall we say a maven-dependency-analyser project in maven-shared? On 23/10/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hey, Sounds good, but I think the most useful form of reuse is a Plexus component. This means it can easily be used in Mojos and any other Maven application that uses Plexus. We can then put it in maven-shared. Definitely sounds useful and allows you to do the "Optimize Dependencies" in the IDE eventually :-) Nice work. Thanks, Jason. On 23 Oct 06, at 6:04 PM 23 Oct 06, Mark Hobson wrote: > Hi there, > > I've written a mojo that analyses the current project's dependencies > against those that are declared in the pom. It uses ASM to determine > the actual class dependencies from the project's compiled classes and > test classes, and then compares these against the classes held within > the project's artifact jars. This produces the following information: > > * Used declared dependencies > * Used undeclared dependencies > * Unused dependencies > > The question is where it should live? Initial suggestions would be > either maven-dependency-plugin, maven-help-plugin or a new maven/mojo > plugin. It currently just outputs this information to the log, but > future extensions could include: > > - Create a report of the dependency analysis > - Rewrite the POM to add used undeclared dependencies > - Rewrite the POM to remove unused dependencies > - Integration to highlight used undeclared and unused dependencies > with: > - maven-project-info-reports-plugin dependency report > - maven-project-info-reports-plugin dependency graph > - m2eclipse POM editor (unused dependencies -> warning annotations > on <dependency> blocks, etc.) > > I can supply a corresponding initial patch if someone could suggest > where it should reside. > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
