We have a couple of modules where a simple bundle is used (stk, newsletter, ldap), and where we have to set the packaging to jar, which is inherently wrong: it creates an "empty" jar artifacts (which is attached to the build and thus uploaded to repositories). If we set those modules to packaging:pom, the assembly still works but is missing the .TXT files from our remote resources.

Additionally, we might want to use runOnlyAtExecutionRoot, to investigate.

Also check why our parent pom also uses the "bundle" goal.

http://maven.apache.org/plugins/maven-remote-resources-plugin/usage.html