JarCasting
JarCasting JarCasting

Neo4j - Bolt Messaging Library V1

Serialization code and definition of messages for Bolt V1

License

License
Categories

Categories

Neo4J Data Databases Messaging Application Layer Libs
GroupId

GroupId

org.neo4j
ArtifactId

ArtifactId

neo4j-bolt-messaging-v1
Last Version

Last Version

2.3.0-RC1
Release Date

Release Date
Type

Type

jar
Description

Description

Neo4j - Bolt Messaging Library V1
Serialization code and definition of messages for Bolt V1
Project URL

Project URL

http://components.neo4j.org/neo4j-bolt-messaging-v1/2.3.0-RC1/neo4j-bolt-messaging-v1
Project Organization

Project Organization

The Neo4j Graph Database Project

Download neo4j-bolt-messaging-v1

Filename Size
neo4j-bolt-messaging-v1-2.3.0-RC1.pom
neo4j-bolt-messaging-v1-2.3.0-RC1.jar 61 KB
neo4j-bolt-messaging-v1-2.3.0-RC1-tests.jar 34 KB
neo4j-bolt-messaging-v1-2.3.0-RC1-test-sources.jar 23 KB
neo4j-bolt-messaging-v1-2.3.0-RC1-sources.jar 45 KB
neo4j-bolt-messaging-v1-2.3.0-RC1-javadoc.jar 253 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/org.neo4j/neo4j-bolt-messaging-v1/ -->
<dependency>
    <groupId>org.neo4j</groupId>
    <artifactId>neo4j-bolt-messaging-v1</artifactId>
    <version>2.3.0-RC1</version>
</dependency>
// https://jarcasting.com/artifacts/org.neo4j/neo4j-bolt-messaging-v1/
implementation 'org.neo4j:neo4j-bolt-messaging-v1:2.3.0-RC1'
// https://jarcasting.com/artifacts/org.neo4j/neo4j-bolt-messaging-v1/
implementation ("org.neo4j:neo4j-bolt-messaging-v1:2.3.0-RC1")
'org.neo4j:neo4j-bolt-messaging-v1:jar:2.3.0-RC1'
<dependency org="org.neo4j" name="neo4j-bolt-messaging-v1" rev="2.3.0-RC1">
  <artifact name="neo4j-bolt-messaging-v1" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.neo4j', module='neo4j-bolt-messaging-v1', version='2.3.0-RC1')
)
libraryDependencies += "org.neo4j" % "neo4j-bolt-messaging-v1" % "2.3.0-RC1"
[org.neo4j/neo4j-bolt-messaging-v1 "2.3.0-RC1"]

Dependencies

compile (2)

Group / Artifact Type Version
org.neo4j : neo4j-bolt-packstream-v1 jar 2.3.0-RC1
org.neo4j : neo4j-bolt-runtime jar 2.3.0-RC1

provided (1)

Group / Artifact Type Version
org.neo4j : neo4j-kernel jar 2.3.0-RC1

test (3)

Group / Artifact Type Version
junit : junit jar 4.11
org.hamcrest : hamcrest-core jar 1.3
org.hamcrest : hamcrest-library jar 1.3

Project Modules

There are no modules declared in this project.

Parent POMs for Neo4j and Friends

What?

The Neo4j Maven project inherits from this parent POM complex. The inheritance includes, but is not limited to, the list of dependencies.

Why?

By having an external parent POM, embedded users can easily share the same dependencies that Neo4j uses, at the same version.

But Why??

Well OK, this parent POM complex has grown a lot of cruft over time. Bear with...

How?

So, to operate the parent POM complex, this is the workflow:

  1. Make your changes to POMs etc., then commit+push them
  2. Run mvn release:prepare --activate-profiles sign-artifacts -Darguments="-Dgpg.keyname=redacted -Dgpg.passphrase=redacted" release:perform
  3. Answer the prompts for release version, repo tag, and next-snapshot version
  4. Log into oss.sonatype.org and close+release the resulting staging repository
  5. Push the commits the release plugin made - the tag is pushed automagically
  6. Rejoice.

Caveats

We use Maven Release Plugin. It is terrible. Here are some things you might need to solve, and the plugin is not helpful in the error messages it gives.

Firstly, there is a sign-artifacts profile that triggers GPG signing of the POMs, which is something Maven Central demands. It is a profile because then it only happens when you ask for it, and not all the time.

  • If you happen to have messed up your local GPG keystore somehow, beware: the error message from GPG plugin are not easy to decode. Best to try with GPG manually to check it works: gpg --sign ... something and gpg --verify ... the signature using the desired GPG key and passphrase that you intend to use for the real deal.
  • Secondly, depending on your passphrase you might have to escape stuff on the command line to get it safely through to the eventual call out to mvn verify that does the actual invokation of GPG plugin and therefore the actual signing

Next, getting access to Nexus over at Sonatype: Maven Deploy Plugin does not support passing in credentials on the command line. Yes you read that right. So here is a workaround.

  • Deploy plugin is going to look in your settings.xml, which normally lives in ``~/.m2/settings.xml`
  • It is going to look for a server entry with id sonatype-nexus-staging for credentials

Other than that, happy hacking!

org.neo4j

Neo4j

Versions

Version
2.3.0-RC1
2.3.0-M03