maven-issues mailing list archives

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

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

Kristian Rosenvold commented on SUREFIRE-667:
---------------------------------------------

It seems to me like these problems also arise due to overuse of wildcard scanning of the classpath.
A lot of people consider wildcard scanning to be a significant antipattern in for instance
spring configuration. If Liferay does this by default I'd recommend filing an issue on Liferay
too.


> 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