thank you for the link – although I already knew this one I tried it a second time, following the Eclipse
instructions very carefully – but I must have missed the very important console information during
Debug run in the past:
OMG – now that I have added MMCoreJ.jar to the project libraries our debugging issue is resolved.
Von: Nicholas Michael Anthony <[hidden email]>
Gesendet: Mittwoch, 30. Oktober 2019 16:13
An: Micro-Manager General <[hidden email]>
Betreff: Re: [micro-manager-general] Eclipse - Debug Environment
All of my experience with plugins has been for MicroManager 2.0 and using Netbeans so I’m not sure how comparable everything is. However, the instructions here have always worked well for me:
Hope that helps,
From: Marco Flachmann <[hidden email]>
Sent: Wednesday, October 30, 2019 9:18 AM
To: [hidden email]
Subject: [micro-manager-general] Eclipse - Debug Environment
I’m fighting to create a clean plugin development environment which consists of
We are using an external build configuration (separate build.xml) to generate the plugin jar-file.
This works nicely.
For debugging purposes I just added the ImageJ source directory as an additional link for the ij library.
And I added an additional debug configuration (Main class: ij.ImageJ, Program arguments: -debug)
Unfortunately this quick approach did not work – after starting our plugin it seems that ImageJ itself runs
Inside of some kind of debug loop: inside the log window I can only see key press events loggings but our
Pugin does not continue.
I found the general approach for debugging purposes to start a separate ImageJ project in Eclipse and
To add a separate project inside workspace for own plugins.
Since we are using git and have several different plugins I’m wondering if this the only approach to have
a nice debugging environment.
Can anyone provide alternative ideas?
Otherwise we have to restructure our git repository dramatically