I would move those dependencies to the project-level instead of plugin-level:
<project> <dependencies/> <build/> </project> Generally I don't attach dependencies to a plugin unless they are truly dependencies of the plugin itself... In this case, these are dependencies of the code, and as such should be moved to the project-level. Wayne On 10/18/06, Devine, James <[EMAIL PROTECTED]> wrote:
Sorry...that is a typo. I get the same error with compile or no tag. -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 12:57 PM To: Maven Users List Subject: Re: Maven 2.0 Classpath Dependency Issue On 10/18/06, Devine, James <[EMAIL PROTECTED]> wrote: > I am new to Maven. I am trying to compile commons-discovery with JDK > 1.5, but the dependent jars don't seem to be in my classpath. Here is > my pom.xml: ... > <scope>compiler</scope> Unless that's a typo, it should either be 'compile' or just left out entirely since 'compile' is the default scope. See: http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html -- Wendy --------------------------------------------------------------------- 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]
