search

imagej / imagej-maven-plugin

[OBSOLETE] All goals migrated to scijava/scijava-maven-plugin
Other
4 stars 6 forks source link

Teach copy-jars about `nar` artifacts #4

Closed dscho closed 5 years ago

dscho commented 10 years ago

When encountering a nar artifact, we should not just ignore it, but rather download it, then look for all platforms known to ImageJ (win32, win64, linux32, linux64 and macosx) and copy the respective attached artifacts -- insofar present -- into the lib/<platform>/ subdirectory.

ctrueden commented 10 years ago

From http://trac.imagej.net/ticket/1928: To be able to build Fiji completely from scratch using Maven (not MiniMaven), we also need to copy the pre-built launcher.

dscho commented 10 years ago

Note that we are really not building anything anymore, but rather let Maven copy the artifacts that are built from the individual components and deployed to the ImageJ Maven repository.

Please also note that the immediate plans are to move away from "building" the complete project. Instead, I would like to see a move to a more Jenkins-based solution: whenever meta-fiji-external-plugins is updated (or pom-fiji), Jenkins should upload the respective new versions to the update site.

Rationale: I need to make sure that yours truly is not required to maintain Fiji. So the knowledge how to maintain it needs to be engrained into scripts and documentation.

ctrueden commented 5 years ago

Closing in favor of scijava/scijava-maven-plugin#19. (We may not need support for NAR artifacts anymore, but we still need support for native libraries embedded in JAR artifacts.)