Details
-
Dependency upgrade
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
archetype-simple-wrj-1.3.1, archetype-quickstart-wrj-1.3.1, objectstore-jdo-1.3.0
-
None
Description
<datanucleus-accessplatform-jdo-rdbms.version>3.3.6</datanucleus-accessplatform-jdo-rdbms.version>
<datanucleus-jodatime.version>3.2.1</datanucleus-jodatime.version>
<datanucleus-maven-plugin.version>3.3.2</datanucleus-maven-plugin.version>
<dependency>
<groupId>org.datanucleus</groupId>
<artifactId>datanucleus-accessplatform-jdo-rdbms</artifactId>
<version>${datanucleus-accessplatform-jdo-rdbms.version}</version>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.datanucleus</groupId>
<artifactId>datanucleus-jodatime</artifactId>
<version>${datanucleus-jodatime.version}</version>
</dependency>
also (according to Andy Jefferson) from 3.3.1, the datanucleus-maven-plugin uses the current (scope="provided") version of datanucleus, which means we can remove the dependency exclusion hacks for that plugin:
<plugin>
<groupId>org.datanucleus</groupId>
<artifactId>datanucleus-maven-plugin</artifactId>
<version>${datanucleus-maven-plugin.version}</version>
<configuration>
<fork>false</fork>
<verbose>true</verbose>
</configuration>
<executions>
<execution>
<phase>compile</phase>
<goals>
<goal>enhance</goal>
</goals>
</execution>
</executions>
</plugin>