0

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.

Community
  • 1
  • 1
Markus Malkusch
  • 7,738
  • 2
  • 38
  • 67

2 Answers2

0

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.

Jean-Rémy Revy
  • 5,607
  • 3
  • 39
  • 65
Markus Malkusch
  • 7,738
  • 2
  • 38
  • 67
0

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 :

Jean-Rémy Revy
  • 5,607
  • 3
  • 39
  • 65
  • So I would store my credentials encrypted in VCS and during build I could decrypt them. Ok, how do other developers work with their credentials? – Markus Malkusch May 26 '15 at 17:48