[MNG-1390] @requiresDependencyResolution in process-classes post compile

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.0
• Component/s: Inheritance and Interpolation
• Assignee: Benjamin Bentmann
• Reporter: Jesse McConnell
• Created: 01/Nov/05 20:24
• Updated: 27/Mar/10 07:31
• Resolved: 27/Mar/10 07:28

Description

I was looking back into some plugins I had written a while back and ran across an oddity.

it appears that when using a plugin in the process-classes phase, after the compiler plugin has done its thing, the @requiresDependencyResolution javadoc flag will toggle the presense of dependencies that are scoped to provided in the dependencies section when calling project.getCompileClasspathElements(); (a difference of 80 vs 24 when not using the flag and then using it)

—

this are two snippits of code from the plugin

/**

• A plugin for generating * java file containing all the classes in a src tree.
  *
• @goal generate
• @requiresDependencyResolution
• @description Functions Generator plugin
• @author jesse <[e-mail]>
  */

List classpathFiles = project.getCompileClasspathElements();

URL[] urls = new URL[classpathFiles.size() + 1];

getLog().debug("" + classpathFiles.size());

for (int i = 0; i < classpathFiles.size(); ++i)

{ getLog().debug((String)classpathFiles.get(i)); urls[i] = new File((String)classpathFiles.get(i)).toURL(); }

urls[classpathFiles.size()] = new File( buildDirectory + "/classes" ).toURL();

URLClassLoader ucl = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader());

being used with the following plugin declaration:

<plugin>
<groupId>gallup.maven</groupId>
<artifactId>services-provider-maven-plugin</artifactId>
<version>1.0.1</version>
<configuration>
<fullyQualifiedFileName>com/g/util/ServiceProvider.java</fullyQualifiedFileName>
</configuration>
<executions>
<execution>
<phase>process-classes</phase>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
</plugin>

---

analyzing the debug output when I run the plugin without the @requiresDependencyResolution I get 80 dependencies and it builds out the classloader correctly..

but if I add the @requiresDependencyResolution statement I go down to 24 dependencies being put into the classloader...and the discrepency corresponds to the presense of the <scope>provided</scope> statement.

Issue Links

• is related to: MNG-3297 maven should not give dependencies to plugins that don't @requireDependencyResolution
• is related to: MNG-4293 Extend Mojo API to allow resolution of both compile and runtime dependencies