Skip to contentPosts
This post is part of a multipart series about creating a graph off all available Maven dependencies.
In the article for the Neo4j extension I described the input for the extension. This article describes the model that is used to create the required JSon. I start of with a small introduction to Vertices and edges before going into the implementation.
Vertices and Edges In mathematics, and more specifically in graph theory, a vertex (plural vertices) or node is the fundamental unit of which graphs are formed: an undirected graph consists of a set of vertices and a set of edges (unordered pairs of vertices), while a directed graph consists of a set of vertices and a set of arcs (ordered pairs of vertices). This post is part of a multipart series about creating a graph off all available Maven dependencies.
Resolving maven dependencies is something we in general leave to our dependency management system, Maven, Ivvy, …. For the purpose to the application we are developing we required a detailed control on how the the dependencies are resolved and the JSon representation of this sub-graph. I start off with a short intro on where to find documentation on the Maven resolving mechanism and then go into the details for each of the parts that are required to do so. Ever had a project that you want to share with every body and not want them to get your source code, build and install it public repository?
For quite some time there you can do this.
Just visit the url: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide follow all the instructions and within 3 days you are up and running and publishing you own artifact in the maven public repository.
Note:
When using a linux environment with github as a scm read: http://help.