[
https://jira.codehaus.org/browse/MRRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312578#comment-312578
]
Mark Derricutt commented on MRRESOURCES-61:
-------------------------------------------
+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 :)
> processed resources are added to main and test resources
> --------------------------------------------------------
>
> Key: MRRESOURCES-61
> URL: https://jira.codehaus.org/browse/MRRESOURCES-61
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Windows 7
> Reporter: David Tombs
> Priority: Minor
> Attachments: mrreserouces-61-project.zip
>
>
> When <attached> is set to true, Maven Remote Resources Plugin adds processed
> resources to both the main and test resources directories. I see no reason to
> add the resources to the test directory unless explicitly specified because
> the test classpath by default includes the main resources as well. The
> disadvantage to including the resources in both the main and test directories
> is that you end up with duplicate files on the class path which, for example,
> can make logback complain about multiple "logback.xml" files.
> The code in question is on lines 533-534 of ProcessRemoteResourcesMojo.java.
> If you need an example project I can make one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
