Spring Data Neo4j - AspectJ Advanced Mapping

Advanced Mapping support for Spring Data Neo4j

License

License

Categories

Categories

Neo4J Data Databases
GroupId

GroupId

org.springframework.data
ArtifactId

ArtifactId

spring-data-neo4j-aspects
Last Version

Last Version

3.4.6.RELEASE
Release Date

Release Date

Type

Type

jar
Description

Description

Spring Data Neo4j - AspectJ Advanced Mapping
Advanced Mapping support for Spring Data Neo4j
Project Organization

Project Organization

Pivotal Software, Inc.

Download spring-data-neo4j-aspects

How to add to project

<!-- https://jarcasting.com/artifacts/org.springframework.data/spring-data-neo4j-aspects/ -->
<dependency>
    <groupId>org.springframework.data</groupId>
    <artifactId>spring-data-neo4j-aspects</artifactId>
    <version>3.4.6.RELEASE</version>
</dependency>
// https://jarcasting.com/artifacts/org.springframework.data/spring-data-neo4j-aspects/
implementation 'org.springframework.data:spring-data-neo4j-aspects:3.4.6.RELEASE'
// https://jarcasting.com/artifacts/org.springframework.data/spring-data-neo4j-aspects/
implementation ("org.springframework.data:spring-data-neo4j-aspects:3.4.6.RELEASE")
'org.springframework.data:spring-data-neo4j-aspects:jar:3.4.6.RELEASE'
<dependency org="org.springframework.data" name="spring-data-neo4j-aspects" rev="3.4.6.RELEASE">
  <artifact name="spring-data-neo4j-aspects" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.springframework.data', module='spring-data-neo4j-aspects', version='3.4.6.RELEASE')
)
libraryDependencies += "org.springframework.data" % "spring-data-neo4j-aspects" % "3.4.6.RELEASE"
[org.springframework.data/spring-data-neo4j-aspects "3.4.6.RELEASE"]

Dependencies

compile (16)

Group / Artifact Type Version
org.springframework : spring-tx jar
org.springframework : spring-context jar
org.springframework : spring-beans jar
org.springframework : spring-aspects jar
org.springframework : spring-aop jar
org.springframework : spring-core jar
javax.validation : validation-api Optional jar 1.0.0.GA
org.springframework.data : spring-data-neo4j jar 3.4.6.RELEASE
org.hibernate.javax.persistence : hibernate-jpa-2.0-api Optional jar 1.0.0.Final
org.aspectj : aspectjrt jar 1.8.9
org.neo4j » neo4j-spatial Optional jar 0.14-neo4j-2.2.3
org.neo4j : neo4j-cypher-dsl jar 2.0.1
org.neo4j : neo4j jar 2.2.5
javax.transaction : javax.transaction-api jar 1.2
commons-io : commons-io jar 2.4
org.slf4j : slf4j-api jar 1.7.21

runtime (1)

Group / Artifact Type Version
org.slf4j : jcl-over-slf4j jar 1.7.21

test (10)

Group / Artifact Type Version
org.hibernate : hibernate-validator jar 4.2.0.Final
org.springframework.data : spring-data-neo4j test-jar 3.4.6.RELEASE
org.neo4j : neo4j-kernel test-jar 2.2.5
org.neo4j : neo4j-io test-jar 2.2.5
org.hamcrest : hamcrest-library jar 1.3
org.hamcrest : hamcrest-core jar 1.3
junit : junit jar 4.12
org.mockito : mockito-core jar 1.10.19
org.springframework : spring-test jar
ch.qos.logback : logback-classic jar 1.1.7

Project Modules

There are no modules declared in this project.

Spring Data Build Infrastructure icon?job=spring data build%2Fmaster&subject=Build

This repository contains common infrastructure to be used by Spring Data modules that build with Maven. It consists of a resources project that bundles up resources that are needed during the build CSS for reference documentation generation and JavaDoc. The second project is parent that can be used as parent project to pre-configure core dependencies, properties, reference documentation generation and most important of all the appropriate distribution assembly.

The parent project can be eased for either a single-module Maven project or a multi-module one. Each of the setups requires a slightly different setup of the project.

Code of Conduct

This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to [email protected].

Project setup

General setup

The parent project configures the following aspects of the project build:

Shared resources are pulled in from the spring-data-build-resources dependency (images, CSS, JavaScript). Renders reference documentation from Asciidoc file named index.adoc within src/asciidoc. In the distribute profile, two assemblies are generated: A ZIP to be uploaded to docs.spring.io (incl. javadoc (browsable), reference docs as described before) with the following content:

- changelog.txt
- notice.txt
+ reference -> Asciidoc generated reference documentation
  + html
  + pdf
  + epub
+ api -> JavaDoc

A second ZIP is generated to be uploaded to docs.spring.io to contain all Spring namespace XSDs.

The following dependencies are pre-configured.

  • Logging dependencies: SLF4j + Commons Logging bridge and Logback as test dependency

  • Test dependencies: JUnit / AssertJ / Hamcrest / Mockito

  • Dependency versions for commonly used dependencies

Single project setup

If the client project is a project consisting of a single project only all that needs to be done is declaring the parent project:

<parent>
	<groupId>org.springframework.data.build</groupId>
	<artifactId>spring-data-parent</artifactId>
	<version>${most-recent-release-version}</version>
</parent>

Be sure to adapt the version number to the latest release version. The second and already last step of the setup is to activate the assembly and asciidoctor plugin in the build section:

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-assembly-plugin</artifactId>
</plugin>
<plugin>
	<groupId>org.asciidoctor</groupId>
	<artifactId>asciidoctor-maven-plugin</artifactId>
</plugin>

As an example have a look at the build of Spring Data JPA.

Multi project setup

A multi module setup requires slightly more setup and some structure being set up.

  • The root pom.xml needs to configure the project.type property to multi.

  • Asciidoc documentation sources need to be in the root project.

  • The assembly needs to be build in a dedicated sub-module (e.g. distribution), declare the assembly plugin (see single project setup) in that submodule and reconfigure the project.root property in that module to ${basedir}/...

  • Configure ${dist.id} in the root project to the basic artifact id (e.g. spring-data-mongodb) as this will serve as file name for distribution artifacts, static resources etc. It will default to the artifact id and thus usually resolve to a …-parent if not configured properly.

As an example have a look at the build of Spring Data MongoDB.

Build configuration

  • Goals to execute clean (dependency:tree) install -Pci to run the build

  • Goals to execute clean deploy -Pci,artifactory to deploy artifacts to Artifactory

  • A nightly build can then use clean (dependency:tree) deploy -Pdistribute to publish reference documentation

Additional build profiles

  • ci - Packages the JavaDoc as JAR for distribution (needs to be active on the CI server to make sure we distribute JavaDoc as JAR).

  • distribute - Creates Asciidoc documentation.

  • distribute-schema - Creates schema file distribution.

  • spring…-next - Configures the Spring version to be used to be the next Spring Framework snapshot version.

License

Spring Data Build is Open Source software released under the Apache 2.0 license.

org.springframework.data

Versions

Version
3.4.6.RELEASE
3.4.5.RELEASE
3.4.4.RELEASE
3.4.2.RELEASE
3.4.1.RELEASE
3.4.0.RELEASE
3.3.2.RELEASE
3.3.1.RELEASE
3.3.0.RELEASE
3.2.4.RELEASE
3.2.3.RELEASE
3.2.2.RELEASE
3.2.1.RELEASE
3.2.0.RELEASE
3.1.6.RELEASE
3.1.5.RELEASE
3.1.4.RELEASE
3.1.2.RELEASE
3.1.1.RELEASE
3.1.0.RELEASE
3.0.3.RELEASE
3.0.2.RELEASE
3.0.1.RELEASE
3.0.0.RELEASE
2.3.5.RELEASE
2.3.4.RELEASE
2.3.3.RELEASE
2.3.2.RELEASE
2.3.1.RELEASE
2.3.0.RELEASE
2.2.3.RELEASE
2.2.2.RELEASE
2.2.1.RELEASE
2.2.0.RELEASE
2.1.0.RELEASE
2.0.2.RELEASE
2.0.1.RELEASE
2.0.0.RELEASE