Is there a way to remove the last version of a release in an artifact repository when deploy the new version? I mean, imagine that I have deployed version 1.0.0 of com.company.project:project. If I deploy version 1.1.0 of the same artifact, I'd want that version 1.0.0 was deleted. Sorry if it is obvious, I'm newbie in this...
Related
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.
Latest version of gax java (Google Api EXtensions) is 0.3.0 as per gax-java, but there is no jar file found for the same .
Maven Repository lists version 0.2.0 as the latest. Could some one help me out in finding the latest jar version.
Maven repository has posted the latest version.
Recently Sonatype released new version 3.0 of the Nexus repository. On the first look, the new version has quite a bit new features, and most important for is support for npm modules.
However, I quickly realised that there is no way to migrate our current maven repository to a new version as the structure of the repository has been changed. The migration from the version 2 promised to be available in version 3.1, but I cannot find when it is going to happen. We need support for npm and I wonder if I'll start using 3.0 for npm only would it be possible to somehow merge my npm and maven repositories together once 3.1 released?
Nexus 2 does have support for npm, but npm in Nexus 3 has support for some features that nexus 2 doesn't. Go ahead and set up Nexus 3 for npm now, when 3.1 is out you'll be able to migrate your existing Nexus 2 repositories into the Nexus 3 instance.
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).
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.