These are chat archives for fiji/fiji

16th
May 2019
Stephan Preibisch
@StephanPreibisch
May 16 07:42
Hi, since some time I get a deployment error on travis when compiling the multiview-simulation:
[WARNING] The requested profile "deploy-to-scijava" could not be activated because it does not exist.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project multiview-simulation: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
I tried to understand it, but everything seems nearly identical to other projects that are deployed well. Does anybody have an idea what could be going wrong? Thanks so much!
The properties part of the pom.xml is identical to for example the multiview-reconstruction
<properties>
    <package-name>net.preibisch.simulation</package-name>

    <license.licenseName>gpl_v2</license.licenseName>
    <license.copyrightOwners>Multiview Simulation developers.</license.copyrightOwners>

    <!-- NB: Deploy releases to the ImageJ Maven repository. -->
    <releaseProfiles>deploy-to-imagej</releaseProfiles>
</properties>
Jan Eglinger
@imagejan
May 16 09:34
@StephanPreibisch the latest travis-build.sh script relies on deploy-to-scijava being present, so your project needs to depend on pom-scijava-26.0.0 at least. You can use @ctrueden's ij-to-sj.sh script to do the migration.
(Background: maven.imagej.net was migrated to maven.scijava.org)
Jan Eglinger
@imagejan
May 16 09:39
Stephan Preibisch
@StephanPreibisch
May 16 12:06
Ah, ok, makes sense, thanks a lot! In my other projects it is still "deploy-to-imagej” but it yet works, I guess there is some workaround implemented in pom-scijava-26.0.0?
Curtis Rueden
@ctrueden
May 16 14:24
@StephanPreibisch Projects that still depend on older pom-scijava (<26) and use deploy-to-imagej will fail to deploy the built artifact with a 301 (permanent redirect) error. But… those projects you say work—do they do a deploy? Or no?
In any case: the solution is what @imagejan said (thanks @imagejan!!): update to pom-scijava 26 and change deploy-to-imagej to deploy-to-scijava and change maven.imagej.net to maven.scijava.org everywhere. The ij-to-sj.sh linked above does everything you need. Sorry for the hassle. I tried to change over all the projects I knew about, but I was in a hurry so mostly only did the projects in core orgs this time. There are a bunch of projects in other orgs (like PreibischLab) that I often try to update, but I do not have push rights to many of those orgs, so I just skipped it this time. I’ll stop being lazy and do another audit right now and file some PRs so that others do not have to suffer as you have suffered. :scream:
Stephan Preibisch
@StephanPreibisch
May 16 14:59
Hi @ctrueden, projects that deploy-to-imagej but use pom-scijava >= 26 still deploy, but I’ll change it to be compatible
thanks so much for keeping this all running, it is absolutely no problem for me to execute these simple changes :)
Curtis Rueden
@ctrueden
May 16 15:41
@StephanPreibisch Since I have push access to BigStitcher, multiview-reconstruction and multiview-simulation, I took care of those.
I also have a PR about to go for MTrack.
@lacan I want to update ijp-frc but I can’t, since it’s not on GitHub. So take note of the above needed changes please.
Stephan Preibisch
@StephanPreibisch
May 16 16:08
Thanks so much @ctrueden
Curtis Rueden
@ctrueden
May 16 20:39
Finally finished going through all my scijava-community repositories. Everything updated, pushed to master where possible, PRs filed where not, except for imagejfx, which is a tough case due to the usage of JavaFX.
Curtis Rueden
@ctrueden
May 16 21:08
External Fiji projects have now all been updated.
Curtis Rueden
@ctrueden
May 16 21:16
Repositories that still need conversion:
  • ClearVolume/ClearGL @skalarproduktraum
  • ClearVolume/imglib2-clearvolume @skalarproduktraum
  • knime-ip/knip-imglib2-ops @dietzc
  • openspim/* @hkmoon @ctrueden
  • saalfeldlab/bigcat @axtimwalde
  • saalfeldlab/n5-utils @axtimwalde
  • saalfeldlab/n5 @hanslovsky @axtimwalde
  • maarzt/imagej-legacy-course @maarzt
  • skalarproduktraum/sciview-tutorial @skalarproduktraum
Curtis Rueden
@ctrueden
May 16 21:24
Uhhh, I started trying to do PRs for some of the above, but many of those projects have other POM-related issues. I’m going to punt. If you are mentioned above, and care about your build continuing to work, please change maven.imagej.net to maven.scijava.org and update to the pom-scijava 26.0.0 parent.