i don't think the classpath is filtered based on those values in this goal, it just dumps the actual classpath that would match the desired scope.
On Mon, Jan 17, 2011 at 10:52 AM, John Anderson <[email protected]> wrote: > I am trying to use dependency:build-classpath. If I run "mvn > dependency:analyze" all seems fine, but if I do "mvn > dependency:build-classpath", it seems to ignore my configuration. For > example, the scope and outputFileFilter settings are ignored in the second > case. Am I doing something wrong? > > Here is the pertinent part of my pom: > > > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-compiler-plugin</artifactId> > <version>2.0.2</version> > <configuration> > <source>1.6</source> > <target>1.6</target> > </configuration> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-dependency-plugin</artifactId> > <executions> > <execution> > <id>build-classpath</id> > <goals> > <goal>build-classpath</goal> > </goals> > <configuration> > <includeScope>runtime</includeScope> > <excludeScope>test</excludeScope> > <outputFilterFile>true</outputFilterFile> > </configuration> > </execution> > </executions> > </plugin> > </plugins> > </build> > > > --------------------------------------------------------------------- > 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]
