Maven Dependency Plugin
  1. Maven Dependency Plugin
  2. MDEP-128

Support ability to specify multiple "includeScope" parameters

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-alpha-4
    • Fix Version/s: 2.8
    • Component/s: copy-dependencies
    • Labels:
      None

      Description

      You can only configure the plugin with either one includeScope or one excludeScope. When executing the plugin to copy dependencies with the following configuration:

      <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-dependency-plugin</artifactId>
         <executions>
            <execution>
               <id>copy-dependencies</id>
               <phase>validate</phase>
               <goals>
                  <goal>copy-dependencies</goal>
               </goals>
            </execution>
         </executions>
         <configuration>
            <outputDirectory>/src/main/webapp/WEB-INF/lib</outputDirectory> 
            <overWriteReleases>false</overWriteReleases> 
            <overWriteIfNewer>true</overWriteIfNewer> 
            <overWriteSnapshots>true</overWriteSnapshots>
            <excludeScope>provided</excludeScope>
         </configuration>
      </plugin>

      It does exclude the provided scope, but it includes the test scope [easymock, dbunit, and junit appear in the output directory]. I tried to correct this problem by replacing the excludeScope parameter with two includeScope parameters, one for compile one for runtime, but only the first parameter was actually used.

      I also tried to exclude test but got an error, something like, "Can't exclude tests as that would exclude everything!".

      The goal is to be able to recreate the default copy functionality that is accomplished when executing a "mvn package" command, but be able to specify a maven-dependency-plugin configuration. When specifying this configuration, it overrides the default settings throughout the entire build life-cycle (as it should). But it is impossible to configure the plugin in the exact same was as the default settings.

      This is needed to support copying dependencies into the WEB-INF/lib folder within Eclipse workspaces, to support embedded application-server deployment.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Hervé Boutemy
            Reporter:
            Bryan Stopp
          • Votes:
            11 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development