grails-datastore-gorm
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>org.grails</groupId>
<artifactId>grails-datastore-gorm</artifactId>
<version>9.0.0-M3</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!-- This module was also published with a richer model, Gradle metadata, -->
<!-- which should be used instead. Do not delete the following line which -->
<!-- is to indicate to Gradle or any Gradle module metadata file consumer -->
<!-- that they should prefer consuming it instead. -->
<!-- do_not_remove: published-with-gradle-metadata -->
<modelVersion>4.0.0</modelVersion>
<groupId>org.grails</groupId>
<artifactId>grails-datastore-gorm</artifactId>
<version>9.0.0-M3</version>
<dependencies>
<dependency>
<groupId>org.grails</groupId>
<artifactId>grails-datastore-core</artifactId>
<version>9.0.0-M3</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.grails</groupId>
<artifactId>grails-datastore-gorm-validation</artifactId>
<version>9.0.0-M3</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>jakarta.annotation</groupId>
<artifactId>jakarta.annotation-api</artifactId>
<scope>compile</scope>
<version>2.1.1</version>
</dependency>
<dependency>
<groupId>jakarta.persistence</groupId>
<artifactId>jakarta.persistence-api</artifactId>
<scope>compile</scope>
<version>3.1.0</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
<scope>compile</scope>
<version>6.2.2</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-jdbc</artifactId>
<scope>compile</scope>
<version>6.2.2</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-tx</artifactId>
<scope>compile</scope>
<version>6.2.2</version>
</dependency>
<dependency>
<groupId>jakarta.el</groupId>
<artifactId>jakarta.el-api</artifactId>
<version>4.0.0</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.apache.groovy</groupId>
<artifactId>groovy</artifactId>
<scope>runtime</scope>
<version>4.0.25</version>
</dependency>
<dependency>
<groupId>org.hibernate.validator</groupId>
<artifactId>hibernate-validator</artifactId>
<scope>runtime</scope>
<version>8.0.2.Final</version>
</dependency>
<dependency>
<groupId>org.glassfish</groupId>
<artifactId>jakarta.el</artifactId>
<version>4.0.2</version>
<scope>runtime</scope>
</dependency>
</dependencies>
<name>Grails GORM</name>
<description>GORM - Grails Data Access Framework</description>
<url>https://github.com/grails/grails-data-mapping</url>
<licenses>
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
<scm>
<url>https://github.com/grails/grails-data-mapping</url>
<connection>scm:git@github.com:grails/grails-data-mapping.git</connection>
<developerConnection>scm:git@github.com:grails/grails-data-mapping.git</developerConnection>
</scm>
<issueManagement>
<system>Github Issues</system>
<url>https://github.com/grails/grails-data-mapping/issues</url>
</issueManagement>
<developers>
<developer>
<id>graemerocher</id>
<name>Graeme Rocher</name>
</developer>
<developer>
<id>jeffscottbrown</id>
<name>Jeff Brown</name>
</developer>
<developer>
<id>burtbeckwith</id>
<name>Burt Beckwith</name>
</developer>
<developer>
<id>jameskleeh</id>
<name>James Kleeh</name>
</developer>
<developer>
<id>puneetbehl</id>
<name>Puneet Behl</name>
</developer>
<developer>
<id>jamesfredley</id>
<name>James Fredley</name>
</developer>
</developers>
</project>
Open source consumption has exploded, with estimates placing this year’s downloads at over 6.6 trillion. This reliance on open source components, now making up to 90% of the modern software application, has ushered in both unprecedented innovation and complex challenges for software supply chains.
View the Report
