When writing some integration tests, I needed a dummy entity for those tests, to resid

Hmm. OK, yes, that seemed to work. I used: <div class="snippet-clipboard-content

Provide additional goals to enhance test code about datanucleus-maven-plugin HOT 3 CLOSED

datanucleus commented on August 22, 2024 1

Provide additional goals to enhance test code

from datanucleus-maven-plugin.

Comments (3)

danhaywood commented on August 22, 2024

NB: still on DataNucleus 4.1, so need this PR to be applied to the 4.0 code branch please.

from datanucleus-maven-plugin.

andyjefferson commented on August 22, 2024

Not saying this isn't useful but can you not just set property "metadataDirectory" to ${project.build.testOutputDirectory} ???

from datanucleus-maven-plugin.

danhaywood commented on August 22, 2024

Hmm. OK, yes, that seemed to work. I used:

<groupId>org.datanucleus</groupId>
<artifactId>datanucleus-maven-plugin</artifactId>
<version>4.0.1</version>
<configuration>
	<fork>false</fork>
	<log4jConfiguration>logging-dn-enhance.properties</log4jConfiguration>
	<verbose>true</verbose>
</configuration>
<executions>
	<execution>
		<id>process-classes</id>
		<phase>process-classes</phase>
		<goals>
			<goal>enhance</goal>
		</goals>
	</execution>
	<execution>
		<id>process-test-classes</id>
		<phase>process-test-classes</phase>
		<goals>
			<goal>enhance</goal>
		</goals>
		<configuration>
			<metadataDirectory>${project.build.testOutputDirectory}</metadataDirectory>
		</configuration>
	</execution>
</executions>

As I'm unblocked, I don't care too much whether you apply the PR or reject it; I think on balance it's still worth having, but it's fairly marginal.

from datanucleus-maven-plugin.

Recommend Projects