These are chat archives for fiji/fiji

11th
Oct 2016
Curtis Rueden
@ctrueden
Oct 11 2016 03:03
You cannot deploy the same version more than once. Use a -SNAPSHOT suffix in your POM.
Robert Haase
@haesleinhuepf
Oct 11 2016 07:12
@ctrueden Thanks for the hint, but I was trying SNAPSHOTs as well. Furthermore, there is no 1.0.1 version in the repository.
Robert Haase
@haesleinhuepf
Oct 11 2016 07:27
Ok, I just figured out: "maven deploy" did not work, "release_version.sh 1.0.1-SNAPSHOT" did not work. But mvn -U -Pdeploy-to-imagej clean deploy --settings settings.xml does! Furthermore, suprisingly I need no <DistributionManagement> node in my Pom… Thanks to @skalarproduktraum and @ctrueden ! <3
Curtis Rueden
@ctrueden
Oct 11 2016 12:41
Sorry @haesleinhuepf, I should have thought of that profile. Yes, you need it -- it adds the proper distributionManagement.
Robert Haase
@haesleinhuepf
Oct 11 2016 12:44
Thanks for supporting me. It’s sometimes quite annoying, when you don’t know what’s the actual issue… I was just running out of ideas what to try next ;-)
Curtis Rueden
@ctrueden
Oct 11 2016 12:46
Oh, from the error, you must have already had the right repo configured. The 400 means either "invalid user/pass" or "release artifact already exists" in my experience.
Robert Haase
@haesleinhuepf
Oct 11 2016 12:50
I had some explicit “Authentication errors” in the very beginning… And: the artifact never existed in the repository - there is still no version 1.0.1 inside… http://maven.imagej.net/#nexus-search;quick~binaryops
I guess the issue was something different.
But it’s solved. Don’t mind ;-)