maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lisak (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources
Date Tue, 04 Jan 2011 11:05:58 GMT

    [ http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250359#action_250359
] 

lisak commented on SUREFIRE-667:
--------------------------------

Yeah, I also needed surefire-plugin to do this many times. It often can be done differently
in some way or another but it complicates things ..

> Setting up maven resources when testing in addition to testResources
> --------------------------------------------------------------------
>
>                 Key: SUREFIRE-667
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-667
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.6
>            Reporter: vychtrle
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message