The best way is to check out this particular git branch and build your own copy using Git and Maven.
Once you have Git and Maven installed:
git clone https://github.com/bonej-org/BoneJ2.git
Gets you following the official release repository copied into a directory called
cd into it.
git remote add mdoube-bonej https://github.com/mdoube/BoneJ2.git
Creates a new ‘remote’, which tracks my personal fork of BoneJ2
git fetch mdoube-bonej
Refreshes your local copy of my fork with updated commit and branch information (i.e. whatever work I was just doing).
git checkout mdoube-bonej/particle-analyser
Loads all the up-to-date code on my
particle-analyser branch, which is where I’m working on these Particle Analyser features.
./IJinstall_naughty.sh <path to your>/Fiji.app/
Installs BoneJ plugins to your Fiji, using whatever code you happen to have checked out with Git. Replace
<path to your> with the directory path to Fiji on your system.
Restart Fiji and try the plugins. We’ve built this on Ubuntu, but it ought to work elsewhere (Mac OS X, Windows I guess).
git branch -a
Lists all the branches available for you to check out in case you want to try something else.
git checkout master
Gets you back to the release branch of your copy of
Updates your branch with new commits from the remote.
There are tons of Git tutorials about. If you want to start contributing to BoneJ, you will need to make a fork on GitHub and clone that; that will be your ‘origin’. You would then push your commits (code changes) to your fork, and send us a pull request by asking to merge your commits into
Let us know how you get on with these instructions - they could form the basis of a Wiki entry for bleeding edge testers like you.