Maven-dependency-plugin (unpack-dependencies) ignores configuration

Question

The following problem occurred: There is a dependency in the project. The dependency contains .js and .css files (essentially they will be used as resources). I need to extract and put these files in a certain place. I thought to use maven-dependency-plugin for this, but it does not use the configuration I specified (use defaults). Please tell me where I could be wrong.

pom.xml:

<dependencies>
    <dependency>
        <groupId>my.group.Id</groupId>
        <artifactId>my-artifact-id</artifactId>
        <version>my_version</version>
    </dependency>
</dependencies>

<build>
    <pluginManagement>
        <plugins>
            <plugin>
                <groupId>org.apache.maven</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <version>2.10</version>
                <executions>
                    <execution>
                        <id>unpack</id>
                        <phase>generate-resources</phase>
                        <goals>
                            <goal>unpack-dependencies</goal>
                        </goals>
                        <configuration>
                            <includeScope>runtime</includeScope>
                            <includeGroupIds>my.group.Id</includeGroupIds>
                            <includeArtifactIds>my-artifact-id</includeArtifactIds>
                            <includes>**/*.js,**/*.css</includes>
                            <outputDirectory>${project.basedir}/my/path</outputDirectory>
                            <overwriteReleases>true</overwriteReleases>
                            <overwriteSnapshots>true</overwriteSnapshots>
                            <overwriteIfNewer>true</overwrteIfNewer>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </pluginManagement>
</build>

Answer 1

You are declaring your plugin execution inside a <pluginManagement> section. This section is great for putting configuration in one place and reusing it later, but it won't execute your plugin.

Try this:

  <build>
      <pluginManagement>
          <plugins>
              <plugin>
                  <groupId>org.apache.maven.plugins</groupId> <!-- your example contained a typo. -->
                  <artifactId>maven-dependency-plugin</artifactId>
                  <version>2.10</version>
                  <executions>
                      <execution>
                          <id>unpack</id>
                          <phase>generate-resources</phase>
                          <goals>
                              <goal>unpack-dependencies</goal>
                          </goals>
                          <configuration>
                              <includeScope>runtime</includeScope>
                              <includeGroupIds>commons-lang</includeGroupIds>
                              <includeArtifactIds>commons-lang</includeArtifactIds>
                              <includes>**/*.js,**/*.css</includes>
                              <outputDirectory>${project.basedir}/my/path</outputDirectory>
                              <overwriteReleases>true</overwriteReleases>
                              <overwriteSnapshots>true</overwriteSnapshots>
                              <overwriteIfNewer>true</overwriteIfNewer> <!-- Typo in your POM here as well -->
                          </configuration>
                      </execution>
                  </executions>
              </plugin>
          </plugins>
      </pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-dependency-plugin</artifactId>
        </plugin>
      </plugins>
   </build>