How to copy unversioned test resources during release:perform?

StackOverflow https://stackoverflow.com/questions/20515584

  •  31-08-2022
  •  | 
  •  

Question

My Question is very similar to "Maven doesn't copy untracked resources while releasing". I have test resources which are not under version control. As testing is part of release:perform that fails without those resources.

How can I tell Maven to copy those unversioned test resources into target/checkout/target/test-classes/. I really would prefer not to skip testing. Those test resource won't come into the public vcs as they have credentials for a webservice.

Was it helpful?

Solution

There seems to be many ways to achieve this. One way is with the maven-resources-plugin and a profile. The release-plugin sets during release:perform the profile release-plugin. You simply have add the maven-resources-plugin into that profile (or a custom profile which is activated by <releaseProfiles>).

<plugin>
    <artifactId>maven-resources-plugin</artifactId>
    <version>2.6</version>
    <executions>
        <execution>
            <id>copy-resources</id>
            <phase>validate</phase>
            <goals>
                <goal>copy-resources</goal>
            </goals>
            <configuration>
                <outputDirectory>${project.build.directory}/test-classes</outputDirectory>
                <resources>
                    <resource>
                        <directory>${basedir}/../../src/test/resources/</directory>
                    </resource>
                </resources>
            </configuration>
        </execution>
    </executions>
</plugin>

With org.sonatype.oss:oss-parent it's a bit different, as that parent disables <useReleaseProfile> but uses sonatype-oss-release.

OTHER TIPS

Just as a quick reply :

You SHOULD not include unversionned resources. This is not Maven philisophy ... indeed you MUST not :).

and aimed to provide repeatable build. You CANNOT ensure that your build will ever deliver the same result if you rely on unversioned, let say uncontroled, resources.

For later purposes, credentials can be encrypted easily :

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top