I cloned the neo4j-contrib/spatial repo on github, but the recommended "mvn install" doesn't work--it breaks on a bunch of missing files and symbols (e.g. "package org.neo4j.index.impl.lucene does not exist").
The pom.xml file in the repo references neo4j 3.0.0, but I'm running neo4j 2.3.1 on Ubuntu 15.04. Neo4j 3.0.0 is not yet listed as a stable release.
There is a separate repo of releases for neo4j-spatial at neo4j-contrib/m2, including one targeting neo4j-2.3.0, but having cloned the repo, it's not clear whether or how to use this to get the mvn install to work.
Any tips?
Which branch are you trying to build? This branch is the release targeting Neo4j 2.3 and should build fine. If you aren't able to build please submit a Github issue with the error(s).
For installing the server plugin there are pre-compiled versions of the JAR files available here that you can just unzip and drop in the /plugins directory. The most recent targets Neo4j 2.3. This should work fine with Neo4j 2.3.1 (I used this neo4j-spatial release with Neo4j 2.3.1 for a project last week without any problems).
Related
I have a situation where my system has one maven installed (e.g version 3.7.1. I have some projects that needs that version so this version is my default and if I build a project using mvn the version 3.7.1 is used by default to build the project.
Now I have to work on a project where it needs maven version 3.8.1 and I am looking for a way to do it. I am planning to install the maven version 3.8.1 in same system and would like to call this maven while building the new project. Can anyone help me on how to add envionment variable for new maven and call it whenever necessary while building without removing the 3.7.1 version
Aside from having separate Maven installations on your system, you could also have a look at the Maven Wrapper.
The maven wrapper allows you to attach a small script to your code base, which downloads and runs a specific version of Maven. In this way there are no dependencies to any Maven installations on your system.
After placing the Maven Wrapper in your project, you would then simply run ./mvnw install instead of mvn install.
I am using SDKMAN to manage different versions of maven or java. SDKMAN is a tool for managing parallel versions of multiple Software Development Kits on most Unix based systems. It provides a convenient Command Line Interface (CLI) and API for installing, switching, removing and listing Candidates.
It is very convenient and this problem no longer exists for me.
I am trying to use maven in our project and am new to it.
checking this https://maven.apache.org/download.cgi
3.6.0 version is latest version to download.
Someone was saying there is maven 4 is latest. Not sure where to download this from and can we use this for java 8.
Which one is latest version to use?
From https://maven.apache.org/download.cgi
Apache Maven 3.6.0 is the latest release and recommended version for
all users.
Works nicely with Java 8. Note that your IDE may bundle an older version in the unlikely case you run into problems.
Is there a way to update the maven distribution without re-downloading the newer version and fixing the new path in the environment path?
something like: mvn selfupdate (the macport style)
No, but the Maven install is only a very thin bootstrap anyway.....
Maven downloads most of it's functionality as plugins. This normally happens when you run your first build and stores them in a local repository under:
$HOME/.m2/repository
So the good news is that when you install the new version of Maven, it will re-use the plugins already downloaded (unless newer ones are required).
Finally if you have concerns about performance it's an excellent idea to install a Maven repository manager. Software like Nexus can proxy and cache external repositories like Maven Central and will significantly improve your build performance (and enable off-line builds). Nexus is very lightweight, I run it on my laptop.
I am getting this error in a Maven build (mvn clean install) on a Mac with Mountain Lion
org.tmatesoft.svn.core.SVNException: svn: The path 'XYZ' appears to be part of Subversion 1.7 (SVNKit 1.4) or greater
working copy rooted at '/Users/XYZ/workspace/XYZ'.
Please upgrade your Subversion (SVNKit) client to use this working copy.
I had SVN installed as part of the Apple Command Line tools package and that gets installed at /usr/bin. I have installed the latest SVN as well but that got installed at /usr/local/bin.
When the maven build runs, it does not pick up the latest SVN, it picks the older one and fails.
Has anyone faced this kind of problem before?
I think there are 2 options -
1) Somehow force maven to use the new installed SVN.
2) Upgrade the SVN installed as part of Apple' Command Line tools to the latest SVN. I have reinstalled Command Line tools with the latest version but it still sticks to the older version.
I dont control the pom.xml so modifying it is not a viable option.
Any pointers in resolving this would be much appreciated.
Thanks!
This means your svn client is version 1.7 but the working copy(your project workspace) was checkout with the older version.
It's simple by execute the following command at your project root directory, where the pom.xml is there.
svn upgrade
please note, the maven use the svn client which is in your OS path.
After upgrade you should configure your IDE to use the version 1.7 as well. In my case I use the Eclipes Juno sr1 with Svnkit.
Anyhow if you would not like to change the working copy or IDE configuration. There is an alternative by install the svn clinet 1.4/1.5/1.6 and set it active via OS path instead.
I hope this may help.
Regards,
Charlee Ch.
For example if I have transitive('xxx:xxx:jar:1.4-SNAPSHOT') in artifacts.rb I don't want that when I run buildr to recive new version of 1.4-SNAPSHOT.
For buildr 1.4.0 no new version was download when I run buildr, but with buildr 1.4.4 it download new version if exist.
The whole idea of making a dependency as a SNAPSHOT dependency is for it to be updated when changed.
As to why buildr-1.4.4 downloads SNAPSHOT updates and 1.4.0 does not, this was introduced in buildr-1.4.2 as per this link.
You could run buildr in offline mode (-o) so that it does not download any updates.