maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Maki (JIRA)" <>
Subject [jira] Commented: (MRESOURCES-131) Maven resources plugin does not honour maven.test.skip flag
Date Wed, 01 Jun 2011 00:58:22 GMT


Ryan Maki commented on MRESOURCES-131:

The biggest problem from not honoring the flag is definitely seen when there are very large
test data files to copy. It can also be a performance problem on certain operating systems
if there are a lot of small files. Even when the tests are skipped these files fill up the
./target and the build never touches them. In one of my builds I can see Maven pause on the
testResources step over and over throughout the lengthy build, even when I'm just running
a quick 'mvn install -Dmaven.test.skip' to get the current artifacts into my local repository
when I've synced changes.

(+1 obviously, many thanks for considering)

> Maven resources plugin does not honour  maven.test.skip  flag
> -------------------------------------------------------------
>                 Key: MRESOURCES-131
>                 URL:
>             Project: Maven 2.x Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 2.4.3
>            Reporter: Kostis Me
> According to the official Maven documention the flag maven.test.skip means that tests
will not be compiled at all.
> If tests are not compiled then there is no need for the resources plugin to copy the
test resources in the output folder.
> This has a dentrimental effect to Maven project with thousands of integration tests that
use a lot of resources (e.g XML files, ZIP files, images.)
> The reason for this is that even if one uses the maven.test.skip flag in order to speed
up the build, the maven resources plugin still takes a lot of time copying the test resources.
> It makes no sense for the plugin to copy the test resource if they are not going to be
used at all (the maven.test.skip flag)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message