processed resources are added to main and test resources

yup if you have a sample project to reproduce the issue, that will be appreciated

If you run 'mvn package' on the attached multi-module project, you will see a warning from logback that logback.xml is on the classpath twice. You will also see logback.xml in target/classes and target/test-classes.

I had a look at this and I think that we need a more advanced solution. Here's another use case that shows why.

We have a resource bundle that consists of ddl and sql files that are used to set up a small database for unit testing. We really don't want these files to be in the main resources directory - only the test resources directory. In version 1.3 of the plugin they end up in both, as described in the title of this issue. This use case is sort of the reverse of the one described by David.

I propose that we add a configuration parameter that let you say in which resource directories the bundle should be unpacked, like this:

<configuration>
  <!-- Comma separated list of values.
       Allowed values: "main" and/or "test"
       Default value: "main,test" -->
  <resourceOutputDirectories>main</resourceOutputDirectories>
</configuration>

+1 for this. In my instance I'm only wanting the remote resources to be in my test resources. I have several projects that all want to reuse/share a set of test files so using remote-resources works well, if only they didn't end up in my production jar