 | | | Subject: Re: maven exec plug-in and the scope of dependency | Subject: Re: maven exec plug-in and the scope of dependency 2007-10-03 - By Wayne Fay
Back
Are you sure its a bug? Did you file the bug in JIRA? Only bugs in
JIRA will ever get dealt with by the dev team.
Wayne
On 10/3/07, Yan Huang <azyhuang@(protected)> wrote:
> Does anyone know if this defect would be fixed soon in exec plug-in? Right
> now, I have to define all of test dependencies (including versions) within
> plug-in, which is kind of pain of neck and not flexible since i have to
> hard-code the dependency version ...
>
> On 9/18/07, Wayne Fay <waynefay@(protected)> wrote:
> >
> > 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 <azyhuang@(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 (See http://tor-5.ora-code.com).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: users-unsubscribe@(protected)
> > For additional commands, e-mail: users-help@(protected)
> >
> >
>
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
|