How to configure JPA for testing in Maven

by

The following will work for Maven 2.1+ (prior to that there wasn’t a phase between test and package that you could bind an execution to).

You can use the maven-antrun-plugin to replace the persistence.xml with the test version for the duration of the tests, then restore the proper version before the project is packaged.

This example assumes the production version is src/main/resources/META-INF/persistence.xml and the test version is src/test/resources/META-INF/persistence.xml, so they will be copied to target/classes/META-INF and target/test-classes/META-INF respectively.

It would be more elegant to encapsulate this into a mojo, but as you’re only copying a file, it seems like overkill.

<plugin>
  <artifactId>maven-antrun-plugin</artifactId>
  <version>1.3</version>
  <executions>
    <execution>
      <id>copy-test-persistence</id>
      <phase>process-test-resources</phase>
      <configuration>
        <tasks>
          <!--backup the "proper" persistence.xml-->
          <copy file="${project.build.outputDirectory}/META-INF/persistence.xml" tofile="${project.build.outputDirectory}/META-INF/persistence.xml.proper"/>
          <!--replace the "proper" persistence.xml with the "test" version-->
          <copy file="${project.build.testOutputDirectory}/META-INF/persistence.xml" tofile="${project.build.outputDirectory}/META-INF/persistence.xml"/>
        </tasks>
      </configuration>
      <goals>
        <goal>run</goal>
      </goals>
    </execution>
    <execution>
      <id>restore-persistence</id>
      <phase>prepare-package</phase>
      <configuration>
        <tasks>
          <!--restore the "proper" persistence.xml-->
          <copy file="${project.build.outputDirectory}/META-INF/persistence.xml.proper" tofile="${project.build.outputDirectory}/META-INF/persistence.xml"/>
        </tasks>
      </configuration>
      <goals>
        <goal>run</goal>
      </goals>
    </execution>
  </executions>
</plugin>

More Related Contents:

  1. Before and After Suite execution hook in jUnit 4.x
  2. How do I get my Maven Integration tests to run
  3. How to build a jar using maven, ignoring test results? [duplicate]
  4. How to properly use findBySomeOtherId not findById in Spring data jpa?
  5. Hibernate Annotations – Which is better, field or property access?
  6. Controlling Maven final name of jar artifact
  7. What is this spring.jpa.open-in-view=true property in Spring Boot?
  8. Convert Existing Eclipse Project to Maven Project
  9. Bypass GeneratedValue in Hibernate (merge data not in db?)
  10. How does the FetchMode work in Spring Data JPA
  11. Difference of Maven JAXB plugins
  12. JDK tools.jar as maven dependency
  13. How to add an extra source directory for maven to compile and include in the build jar?
  14. How do I add a new sourceset to Gradle?
  15. How to test code dependent on environment variables using JUnit?
  16. @GeneratedValue polymorphic abstract superclass over MySQL
  17. “Unmappable character for encoding UTF-8” error
  18. Using maven to output the version number to a text file
  19. Should JPA Entity Manager be closed?
  20. How to include local jar files in Maven project [duplicate]
  21. GenerationType.AUTO vs GenerationType.IDENTITY in hibernate
  22. Add a dependency in Maven
  23. Native query with named parameter fails with “Not all named parameters have been set”
  24. UNION to JPA Query
  25. When should EntityManagerFactory instance be created/opened?
  26. @BatchSize a smart or stupid use?
  27. Error creating bean with name ‘entityManagerFactory
  28. How can I get Maven to stop attempting to check for updates for artifacts from a certain group from maven-central-repo?
  29. What properties does @Column columnDefinition make redundant?
  30. JPA Updating Bidirectional Association

Leave a Comment