Hi there
I am interested in working with ImageJ for developing and teaching and I would like to stay connected to the latest releases of ImageJ. Though I 've found the Daily Build Source site on the Web, I would prefer an access to a version control system like SVN or CVS to check out the sources and any changes automatically. Is it possible ? Best regards, Reinhard -- Reinhard Meyer E-Mail: [hidden email] |
On Oct 9, 2009, at 6:51 AM, Reinhard Meyer wrote:
> Hi there > > I am interested in working with ImageJ for developing and teaching > and I would like to stay connected to the latest releases of ImageJ. > Though I 've found the Daily Build Source site on the Web, I would > prefer an access to a version control system like SVN or CVS to > check out the sources and any changes automatically. Is it possible ? Johannes Schindelin maintains an ImageJ Git source version control repository at http://pacific.mpi-cbg.de/cgi-bin/gitweb.cgi?p=ImageJA.git;a=shortlog;h=refs/heads/imagej -wayne |
Johannes,
For those of us who'd like to pull in Wayne's changes to the ImageJ source to keep an updated version locally, what is the correct way to request them from the git repo? Mike Wayne Rasband wrote: > On Oct 9, 2009, at 6:51 AM, Reinhard Meyer wrote: > >> Hi there >> >> I am interested in working with ImageJ for developing and teaching >> and I would like to stay connected to the latest releases of ImageJ. >> Though I 've found the Daily Build Source site on the Web, I would >> prefer an access to a version control system like SVN or CVS to >> check out the sources and any changes automatically. Is it possible ? > > Johannes Schindelin maintains an ImageJ Git source version control > repository at > > http://pacific.mpi-cbg.de/cgi-bin/gitweb.cgi?p=ImageJA.git;a=shortlog;h=refs/heads/imagej > > -wayne -- Dr Michael Doube BPhil BVSc PhD MRCVS Research Associate Department of Bioengineering Imperial College London South Kensington Campus London SW7 2AZ United Kingdom Phone: +44 (0)20 7594 7426 Fax: +44 (0)20 7594 9817 |
On Monday 12 October 2009 11:39:44 Michael Doube wrote:
> For those of us who'd like to pull in Wayne's changes to the ImageJ > source to keep an updated version locally, what is the correct way to > request them from the git repo? Are you are talking about ImageJA, the one used by Fiji? If so, ImageJA is a submodule of Fiji, so I suppose this is: git submodule init ImageJA git submodule update ImageJA I later found there is a different way explained here: http://pacific.mpi-cbg.de/wiki/index.php/Git_submodule_tutorial Not sure which way is best, I used the first and it works. I hope Johannes will correct me if this is not right. I do not know if there is also an ImageJ (i.e. not "A") git project. But in any case (I hope I got this right), ImageJA is not automatically updated with the daily build changes. I think Johannes incorporates these every so often (although this is *very* often). Alternatively, in linux, you can download the ImageJ daily build source from Wayne's site with the following script: #!/bin/bash wget -r -np rsb.info.nih.gov/ij/source/ but you would not see what are the version differences, obviously. I hope it helps. Gabriel |
In reply to this post by Michael Doube
Hi,
On Mon, 12 Oct 2009, Michael Doube wrote: > For those of us who'd like to pull in Wayne's changes to the ImageJ > source to keep an updated version locally, what is the correct way to > request them from the git repo? Please keep in mind that my primary focus is ImageJA, in particular the 'fiji' branch. Disclaimer: this will be a short Git tutorial. So if you want to track ImageJ using ImageJA's 'imagej' branch, this is what you should do: 1) install Git :-) 2) git clone git://pacific.mpi-cbg.de/ImageJA.git (after this, a directory "ImageJA" will be there, with _ImageJA_ checked out) 3) cd ImageJA 4) git checkout --track origin/imagej (now you will have the current ImageJ checked out) Whenever you feel you want to update now, run N) git pull This will update your current checked out ImageJ to whatever is in the 'imagej' branch. Note that I import ImageJ manually everytime I read that Wayne released a new version, so there may be a lag between official release and update of said branch, such as was the case with 1.43h: it was released on Saturday, but I was offline then and only able to import it early Monday. Ciao, Dscho |
In reply to this post by Gabriel Landini
Hi,
On Mon, 12 Oct 2009, Gabriel Landini wrote: > I do not know if there is also an ImageJ (i.e. not "A") git project. To the best of my knowledge, there is not. > But in any case (I hope I got this right), ImageJA is not automatically > updated with the daily build changes. I think Johannes incorporates > these every so often (although this is *very* often). To make this a bit more explicit: I will include changes from the daily version (or our automatic version of that, downloaded from ImageJ's website several times a day, stored in the 'current' branch) upon demand. So if you say "I need the feature X Wayne implemented in the daily build already, in Fiji" I will include it. I try to merge the releases from Wayne every once in a while, and the plan is to do it as close to Wayne's release cycle as possible. The 'imagej' branch is a pure side effect of that endeavor. > Alternatively, in linux, you can download the ImageJ daily build source from > Wayne's site with the following script: > > #!/bin/bash > wget -r -np rsb.info.nih.gov/ij/source/ > > but you would not see what are the version differences, obviously. > I hope it helps. As I said, this is the 'current' branch of ImageJA.git. There is unfortunately no good way to connect this 'current' branch with the 'imagej' branch (from time to time, they should be identical, but there are subtle differences). As soon as I will have some time to play with this more, I will try to come up with some automated way to see the relationship between the revisions on 'current' and the ones on 'imagej'. Ciao, Dscho |
Free forum by Nabble | Edit this page |