Re: Eclipse woes

Posted by Mark Hiner on Dec 02, 2015; 4:25pm
URL: http://imagej.273.s1.nabble.com/Eclipse-woes-tp5015004p5015092.html

>I usually do not launch  ImageJ from within Eclipse but run both side by
side. This allows a very efficient edit-compile-run cycle.

I second this!

>I do not use Maven to keep things as simple as possible.

I see the complexity of Maven as a fixed cost. If you have a simple project
and dependency structure it may not make sense to use Maven. As your
complexity grows, paying the Maven cost begins to be more and more
reasonable.

>The setup looks like this:

I like what you're doing here to minimize the hassle of copying jars! I
just want to add that you are supposed to be able to do this in a general
way, for every Mavenized ImageJ project, and also automatically copy
dependencies and clean up duplicate versions.[1]

[1]
http://imagej.net/index.php?title=Developing_Fiji_in_Eclipse&oldid=18706#Option_2:_Install_dependencies

On Wed, Dec 2, 2015 at 9:12 AM, Burger Wilhelm <
[hidden email]> wrote:

> Hello Gabriel,
>
> I have been working with Eclipse in combination with ImageJ with great
> satisfaction for many years, using a very simple setup that works
> flawlessly for all my students and on all types of computers (i.e., is
> fool-proof). I do not use Maven to keep things as simple as possible.
>
> The setup looks like this:
> * Use the <Image> directory as the root of the Eclipse project.
> * Include ij.jar in the Java build path (in Eclipse).
> * Place all additional libraries required into the (new)  <ImageJ>/jars
> folder and include them in the Java build path.
> * Create a source folder 'src' to hold the plugin code. Set up
> <ImageJ>/plugins as its output folder.
> * In 'src' I usually create Java packages (max. 1 level deep) for
> structuring your plugins.
>
> A complete Eclipse project setup like this can be downloaded here:
> https://www.dropbox.com/s/rp36c95xlj23ljo/ImageJ-Eclipse-Project.zip?dl=0
>
> I usually do not launch  ImageJ from within Eclipse but run both side by
> side. This allows a very efficient edit-compile-run cycle.
> If you need to start ImageJ under Eclipse's "umbrella" (e.g. to set
> breakpoints and inspect the runtime stack) this can be done easily with a
> small helper class or running ImageJ's main() method. Which I never found
> to be necessary though...
>
> Hope this is of any help. There is no substitute for a proper IDE,
> compile-time safety etc., I am sure you will never want to miss it again.
>
> Best regards,
> Wilhelm
>
> www.imagingbook.com
>
>
> -----Original Message-----
> From: ImageJ Interest Group [mailto:[hidden email]] On Behalf Of
> Gabriel Landini
> Sent: Mittwoch, 02. Dezember 2015 14:40
> To: [hidden email]
> Subject: Re: Eclipse woes
>
> On Wednesday 25 Nov 2015 14:01:08 Curtis Rueden wrote:
> > The following video tutorial might also be informative, although it is
> > a little outdated now too: https://www.youtube.com/watch?v=XyfE_fVphCs
>
> Hi thanks Curtis,
> I had a go at this. Dowloaded the ImageJA, imported the maven project into
> Eclipse, then somehow it compiled the source code under the
> git/ImageJA/target
>
> However, I do not see how to run the result from Eclipse, do I need to
> specify a launcher or a script file?
>
> Thanks
>
> Gabriel
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html