RE: undeclared dependencies in plugins
I think you're misreading the output. The first thing it prints are the used,declared dependencies. I should probably turn that off by default. Junit and the container are the only ones missing. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 6:02 PM To: Maven Developers List Subject: Re: undeclared dependencies in plugins On 24 Apr 07, at 5:29 PM 24 Apr 07, Dennis Lundberg wrote: > Brian E. Fox wrote: >> As part of the checking for 2.0.6, I ran dependency:analyze >> against the >> plugins. We found that almost all plugins have undeclared >> dependencies. >> Those with undeclared dependencies on plexus-utils will require a >> workaround in maven itself to avoid hosing people. (Jason is going to >> send a separate email) >> Please run maven-dependency-plugin 2.0-alpha-4-SNAPSHOT :analyze >> against >> a plugin if you work on it so you can update the pom appropriately. > > > > Below is the output for maven-idea-plugin. > Should I do something about the "Used undeclared dependencies"? > That doesn't look right. Looking at the POM most of those are there. Plexus utils is even there in the POM. > [INFO] [dependency:analyze] > [INFO] Used declared dependencies: > [INFO]org.apache.maven:maven-plugin-api:jar:2.0.1:compile > [INFO]org.apache.maven:maven-project:jar:2.0.1:compile > [INFO]org.apache.maven:maven-artifact-manager:jar:2.0.1:compile > [INFO]org.apache.maven.wagon:wagon-provider-api:jar:1.0- > alpha-5:compile > [INFO]org.apache.maven:maven-artifact:jar:2.0.1:compile > [INFO]org.codehaus.plexus:plexus-utils:jar:1.1:compile > [INFO]dom4j:dom4j:jar:1.6.1:compile > [INFO]org.apache.maven:maven-model:jar:2.0.1:compile > [INFO] org.apache.maven.shared:maven-plugin-testing-harness:jar:1.0- > beta-1:test > [INFO] Used undeclared dependencies: > [WARNING]junit:junit:jar:3.8.1:compile > [WARNING] org.codehaus.plexus:plexus-container-default:jar:1.0- > alpha-9:compile > [INFO] Unused declared dependencies: > [INFO]None > [WARNING] Potential problems discovered. > [INFO] Found Resolved Dependency / DependencyManagement mismatches: > [INFO]Nothing in DepMgt. > > -- > Dennis Lundberg > > - > 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]
Re: undeclared dependencies in plugins
On 24 Apr 07, at 5:29 PM 24 Apr 07, Dennis Lundberg wrote: Brian E. Fox wrote: As part of the checking for 2.0.6, I ran dependency:analyze against the plugins. We found that almost all plugins have undeclared dependencies. Those with undeclared dependencies on plexus-utils will require a workaround in maven itself to avoid hosing people. (Jason is going to send a separate email) Please run maven-dependency-plugin 2.0-alpha-4-SNAPSHOT :analyze against a plugin if you work on it so you can update the pom appropriately. Below is the output for maven-idea-plugin. Should I do something about the "Used undeclared dependencies"? That doesn't look right. Looking at the POM most of those are there. Plexus utils is even there in the POM. [INFO] [dependency:analyze] [INFO] Used declared dependencies: [INFO]org.apache.maven:maven-plugin-api:jar:2.0.1:compile [INFO]org.apache.maven:maven-project:jar:2.0.1:compile [INFO]org.apache.maven:maven-artifact-manager:jar:2.0.1:compile [INFO]org.apache.maven.wagon:wagon-provider-api:jar:1.0- alpha-5:compile [INFO]org.apache.maven:maven-artifact:jar:2.0.1:compile [INFO]org.codehaus.plexus:plexus-utils:jar:1.1:compile [INFO]dom4j:dom4j:jar:1.6.1:compile [INFO]org.apache.maven:maven-model:jar:2.0.1:compile [INFO] org.apache.maven.shared:maven-plugin-testing-harness:jar:1.0- beta-1:test [INFO] Used undeclared dependencies: [WARNING]junit:junit:jar:3.8.1:compile [WARNING] org.codehaus.plexus:plexus-container-default:jar:1.0- alpha-9:compile [INFO] Unused declared dependencies: [INFO]None [WARNING] Potential problems discovered. [INFO] Found Resolved Dependency / DependencyManagement mismatches: [INFO]Nothing in DepMgt. -- Dennis Lundberg - 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]
Re: undeclared dependencies in plugins
Brian E. Fox wrote: As part of the checking for 2.0.6, I ran dependency:analyze against the plugins. We found that almost all plugins have undeclared dependencies. Those with undeclared dependencies on plexus-utils will require a workaround in maven itself to avoid hosing people. (Jason is going to send a separate email) Please run maven-dependency-plugin 2.0-alpha-4-SNAPSHOT :analyze against a plugin if you work on it so you can update the pom appropriately. Below is the output for maven-idea-plugin. Should I do something about the "Used undeclared dependencies"? [INFO] [dependency:analyze] [INFO] Used declared dependencies: [INFO]org.apache.maven:maven-plugin-api:jar:2.0.1:compile [INFO]org.apache.maven:maven-project:jar:2.0.1:compile [INFO]org.apache.maven:maven-artifact-manager:jar:2.0.1:compile [INFO]org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:compile [INFO]org.apache.maven:maven-artifact:jar:2.0.1:compile [INFO]org.codehaus.plexus:plexus-utils:jar:1.1:compile [INFO]dom4j:dom4j:jar:1.6.1:compile [INFO]org.apache.maven:maven-model:jar:2.0.1:compile [INFO] org.apache.maven.shared:maven-plugin-testing-harness:jar:1.0-beta-1:test [INFO] Used undeclared dependencies: [WARNING]junit:junit:jar:3.8.1:compile [WARNING] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:compile [INFO] Unused declared dependencies: [INFO]None [WARNING] Potential problems discovered. [INFO] Found Resolved Dependency / DependencyManagement mismatches: [INFO]Nothing in DepMgt. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: undeclared dependencies in plugins
http://maven.apache.org/plugins/maven-dependency-plugin/usage.html bottom of the page. -Original Message- From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dillon Sent: Tuesday, March 27, 2007 5:58 PM To: Maven Developers List Subject: Re: undeclared dependencies in plugins Hey, how exactly does one run this? --jason On Mar 23, 2007, at 3:56 PM, Brian E. Fox wrote: > As part of the checking for 2.0.6, I ran dependency:analyze against > the > plugins. We found that almost all plugins have undeclared > dependencies. > Those with undeclared dependencies on plexus-utils will require a > workaround in maven itself to avoid hosing people. (Jason is going to > send a separate email) > > > > Please run maven-dependency-plugin 2.0-alpha-4-SNAPSHOT :analyze > against > a plugin if you work on it so you can update the pom appropriately. > > If I get some time, I'll write issues against the plugins with the > exact > failures. > > > > (resend...I think it got denied because of the size...previous > email had > the output in it) > > > - 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]
Re: undeclared dependencies in plugins
Hey, how exactly does one run this? --jason On Mar 23, 2007, at 3:56 PM, Brian E. Fox wrote: As part of the checking for 2.0.6, I ran dependency:analyze against the plugins. We found that almost all plugins have undeclared dependencies. Those with undeclared dependencies on plexus-utils will require a workaround in maven itself to avoid hosing people. (Jason is going to send a separate email) Please run maven-dependency-plugin 2.0-alpha-4-SNAPSHOT :analyze against a plugin if you work on it so you can update the pom appropriately. If I get some time, I'll write issues against the plugins with the exact failures. (resend...I think it got denied because of the size...previous email had the output in it) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
