[ImageJ-devel] ImageJ2 library set up and referencing?

[Vera Andrejchenko]

Dear Johannes and Jay,

thank you both for the reply, links and the latex documentation.
Yes indeed I did had instantiated ImageJ multiple times..

Now I just tried using one of the tutorial examples:
image-tutorials/add-two-datasets

So I created a new maven project, added the pom file from this link:
https://github.com/imagej/imagej-tutorials/blob/master/add-two-datasets/pom.xml
and the java file from:
https://github.com/imagej/imagej-tutorials/blob/master/intro-to-imagej-api/src/main/java/IntroToImageJAPI.java

and tried to run the application, but I got the following error:
java.lang.NoClassDefFoundError: net/imagej/updater/UploaderService

Is there anything I'm missing?

Thank you!

Greetings,
Vera





On Wed, Aug 6, 2014 at 12:41 PM, Jay Warrick <warrick at wisc.edu> wrote:

> Hi All,
>
> I also wrote this help document for just this purpose. I have not received
> feedback from the ImageJ2 dev crew on it yet, but this is what I learned
> and it really helped me. Also, I wrote this before the OPS stuff was added
> so likely, as I learn this interface too, it should be added as well. Feel
> free to add to the document as it is a work in progress. It is written
> using an online collaborative latex editor. But if you don't know latex and
> want to add a section for a topic I missed, just look at the other sections
> and try to copy what I have done or just add plain text and I'll format for
> you later.
>
> Here is the link.
>
> https://www.writelatex.com/756020pphsxc
>
> Cheers,
>
> Jay
>
> On Aug 6, 2014, at 4:51 AM, Johannes Schindelin <
> Johannes.Schindelin at gmx.de> wrote:
>
> > Hi Vera,
> >
> > On Wed, 6 Aug 2014, Johannes Schindelin wrote:
> >
> >> Due to limitations in ImageJ 1.x' design, the legacy service --
> >> responsible for executing any function in ImageJ 1.x -- can be
> >> instantiated only once per class loader. That means that you have to
> >> *dispose* of a SciJava context offering a legacy service *before* you
> can
> >> instantiate a new context.
> >
> > I completely forgot to mention that the best practice is to instantiate
> > the ImageJ object *once* and then reuse that instance, rather than
> > instantiating a new ImageJ object everytime you want to call ImageJ
> > functionality.
> >
> > Ciao,
> > Johannes
> >
> > _______________________________________________
> > ImageJ-devel mailing list
> > ImageJ-devel at imagej.net
> > http://imagej.net/mailman/listinfo/imagej-devel
>
>


-- 
----------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------
Artificial Intelligence Program at KULeuven, Belgium
grad.ing at The Faculty of Electrical Engineering and Information
Technologies
in Skopje,Macedonia
tel: +32 483 439 906
skype:vercence_zvercence
----------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20140807/5798ac7e/attachment.html>