Can I use wildcards to include/exclude a groupID from the maven dependency plugin's unpack-dependencies goal?

Question

I have a project where some of the dependencies have a secondary artifact that I would like to collect & unpack when making my distribution. By using the type and classifier parameters I was able to find these secondary artifacts, which is great.

The only problem is that the transitive dependency tree is quite large and most of the transitive dependencies do not have this secondary artifact, so the build is taking forever looking for things it will never find.

I would like to restrict the search to only certain groupIDs that could possibly have these secondary artifacts. It seems that the includeGroupIds parameter can not accept wildcards.

Is there any way to use wildcard filtering here, or will I have to live the maintenance chore of explicitly listing every group?

Here's an example of what I have now; note the long & hard to maintain list of included groups:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-dependency-plugin</artifactId>
  <executions>
    <execution>
      <id>unpack-litescale</id>
      <phase>prepare-package</phase>
      <goals>
        <goal>unpack-dependencies</goal>
      </goals>
      <configuration>
        <outputDirectory>${project.build.directory}/${project.build.finalName}/WEB-INF/classes</outputDirectory>
        <classifier>litescale</classifier>
        <type>zip</type>
        <includeGroupIds>com.foo.group1,com.foo.group2,com.foo.group3,com.foo.group4,com.foo.group5,com.foo.group6</includeGroupIds>
      </configuration>
    </execution>
  </executions>
</plugin>

Here's an example of what I want:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-dependency-plugin</artifactId>
  <executions>
    <execution>
      <id>unpack-litescale</id>
      <phase>prepare-package</phase>
      <goals>
        <goal>unpack-dependencies</goal>
      </goals>
      <configuration>
        <outputDirectory>${project.build.directory}/${project.build.finalName}/WEB-INF/classes</outputDirectory>
        <classifier>litescale</classifier>
        <type>zip</type>
        <includeGroupIds>com.foo.*</includeGroupIds>
      </configuration>
    </execution>
  </executions>
</plugin>

Sorry, _I_ don't quite follow. Can you post excerpts from your POM? — Marcel Stör, Jan 10 '13 at 21:02
did you find any solution for this? I've arrived at the same wall. — Herr Derb, Apr 26 '18 at 07:30
@HerrDerb this was two jobs ago so my memory is hazy, but as best I recall we ended up writing a custom mojo instead of using the dependency plugin. — carej, Apr 30 '18 at 14:41

score 2 · Answer 1 · answered Jan 31 '19 at 11:49

It seems that includeGroupIds includes all groupIds having the provided values as prefix. I.e. in your example <includeGroupIds>com.foo</includeGroupIds> should do:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-dependency-plugin</artifactId>
  <version>3.1.0</version>
  <executions>
    <execution>
      <id>unpack-litescale</id>
      <phase>prepare-package</phase>
      <goals>
        <goal>unpack-dependencies</goal>
      </goals>
      <configuration>
        <outputDirectory>${project.build.directory}/${project.build.finalName}/WEB-INF/classes</outputDirectory>
        <classifier>litescale</classifier>
        <type>zip</type>
        <includeGroupIds>com.foo</includeGroupIds>
      </configuration>
    </execution>
  </executions>
</plugin>

score -1 · Answer 2 · edited Oct 01 '13 at 14:40

-1

That's not really possible with Maven in the way you're suggesting. Maven's declarative meaning you'll need to know what you want up-front. You could be a bit creative here by writing specific plugin which will do that. Also look at the Maven Assembly Plugin.

edited Oct 01 '13 at 14:40

carej

596
1
6
18

answered Sep 30 '13 at 20:43

KRK Owner

762
7
16

4

Yes, I would like to **declare** that only groups that match a certain pattern should be included. I don't see how this is inconsistent with the Maven Way. – carej Oct 01 '13 at 14:43

Can I use wildcards to include/exclude a groupID from the maven dependency plugin's unpack-dependencies goal?

2 Answers2