[
https://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360710#comment-360710
]
Tibor Digana commented on SUREFIRE-667:
---------------------------------------
This looks similar to SUREFIRE-770. The people should use Open API with
IsolatedClassLoader in surefire 3.0 and modify the CL as necessary in their
projects.
> Setting up maven resources when testing in addition to testResources
> --------------------------------------------------------------------
>
> Key: SUREFIRE-667
> URL: https://jira.codehaus.org/browse/SUREFIRE-667
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Affects Versions: 2.6
> Reporter: vychtrle
> Fix For: 3.0
>
>
> Hey,
> I think that developers would need resource goal of resource plugin to be set
> up differently for
> test phase, than for build phase. When testing one needs to exclude stuff
> from src/main/resources. It seems it can't be done, testResources goal
> is irrelevant for this because it can't operate on src/main/* and resource
> goal can have only one
> setting in pom definition, that takes effect in both test and build
> phase...
> For example, I'd need following settings to look differently (some
> excludes) in testing phase :
> <resources>
> <resource>
> <directory>${project.basedir}/src/main/java</directory>
> <includes>
> <include>**/*.java</include>
> <include>service.properties</include>
> </includes>
> </resource>
> <resource>
>
> <directory>${project.basedir}/src/main/resources</directory>
> <includes>
> <include>**/*.xml</include>
> <include>**/*.properties</include>
> </includes>
> </resource>
> </resources>
> The ideal behavior would be if one could define "src/main/*" in
> <testResources> but it unfortunately can't be done right now
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
