Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teach copy-jars about `nar` artifacts #4

Closed
dscho opened this Issue Mar 19, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@dscho
Copy link
Member

dscho commented Mar 19, 2014

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

This comment has been minimized.

Copy link
Member

ctrueden commented May 1, 2014

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

This comment has been minimized.

Copy link
Member Author

dscho commented Jul 18, 2014

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.

@dscho dscho removed their assignment Nov 9, 2014

@ctrueden

This comment has been minimized.

Copy link
Member

ctrueden commented Sep 12, 2018

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.)

@ctrueden ctrueden closed this Sep 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.