[MASSEMBLY-865] dependencySet "include" seems to implicitly append wildcards to simple groupId:artifactId values

**[Yoann Rodière](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=yrodiere)** opened **[MASSEMBLY-865](https://issues.apache.org/jira/browse/MASSEMBLY-865?redirect=false)** and commented

When a multi-module project has the following modules:

* prefix
* prefix-suffix
* assembly

... with "prefix-suffix" depending on junit for instance, "prefix" depending on nothing, and "assembly" depending on both "prefix" and "prefix-suffix".

Then adding the following in the assembly descriptor will result in "prefix-suffix.jar" and "junit.jar" being present in "lib/prefix/", while we would only expect it in "lib/prefix-suffix/":

```

lib/prefix
runtime
true
true

test:prefix



lib/prefix-suffix
runtime
true
true

test:prefix-suffix

```

I attached a patch with a failing integration test demonstrating the issue.

Known workaround: use "test:prefix:*" instead of "test:prefix" in the assembly descriptor.

---

**Affects:** 2.6, 3.0.0, 3.1.0

**Attachments:**
- [integration-test.patch](https://issues.apache.org/jira/secure/attachment/12878765/integration-test.patch) (_19.16 kB_)

1 votes, 1 watchers

Start with the attached integration-test.patch and the assembly descriptor's dependencySet include filtering, reproducing the failing case with the three modules and the test:prefix include. Done means the prefix output contains only its intended artifact, while prefix-suffix.jar and junit.jar remain in the prefix-suffix output as expected.

Written by the indexing model from the issue text.