Try adding the mysql dependency to the plugin itself. Seems like the exec plugin is not inheriting the test classpath, only the compile classpath.
Wayne On 9/18/07, Yan Huang <[EMAIL PROTECTED]> wrote: > Hello, > > I have a situation where i define "mysql" dependency with "test" scope as > belows: > > <dependency> > <groupId>mysql</groupId> > <artifactId>mysql-jdbc-connector</artifactId> > <version>5.0.3</version> > <scope>test</scope> > </dependency> > > According to the spec, this jar will be included in the classpath of test > compilation and execution. However, when I'm using maven exec plug-in to > prepare some test tables installation in MySQL DB with the "default" > classpath as part of "test-compile" phase: > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>exec-maven-plugin</artifactId> > <executions> > <execution> > <phase>test-compile</phase> > <goals> > <goal>java</goal> > </goals> > </execution> > </executions> > <configuration> > <mainClass>myexample.foo.test</mainClass> > <arguments> > <argument>install</argument> > </arguments> > </configuration> > </plugin> > > The "mvn test-compile" failed to find "mysql-jdbc-connector-5.0.3.jar", > which suggested that this jar was not available during "test-compile" phase. > After removing "test" scope of that dependency, test-compile phase went > through fine. > > Did anyone observe the similar behavior? was the test-scoped dependency > really not available in "test-compile" phase? > > Thanks > Yan > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
