[ImageJ-bugs] [Bug 1012] Compile and Run Command not currently supported in version 1.49p

[bugzilla at fiji.sc]

http://fiji.sc/bugzilla/show_bug.cgi?id=1012

Curtis Rueden <ctrueden at wisc.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
                 CC|                            |ctrueden at wisc.edu
         Resolution|---                         |WONTFIX

--- Comment #4 from Curtis Rueden <ctrueden at wisc.edu> ---
We do not currently have the resources to make "Compile and Run" work as
expected in ImageJ2. For those curious why, some related technical details can
be seen here:

  https://github.com/imagej/ij1-patcher/issues/31#issuecomment-52185528

The "cannot access java.lang.Object bad class file" error is a different
problem that is new to me. I filed an issue for it here:

  https://github.com/scijava/scripting-java/issues/7

When testing this myself, I received a different error, also new to me, which I
filed at:

  https://github.com/scijava/scripting-java/issues/6

Even before these bugs cropped up, using Java in the Script Editor suffered
from another very serious bug:

   https://github.com/scijava/scripting-java/issues/5

So I would definitely recommend using a dedicated tool such as Eclipse to
develop one's ImageJ plugins. (The Script Editor is best for scripts and
macros.)

Plugin authors should distribute their plugins using an update site
(http://imagej.net/Update_Sites), or at least as a .jar or .class file, rather
than as a .java file.

If you feel you have a compelling use case for the Compile and Run command that
would justify the substantial amount of time required to make it work in
ImageJ2, I invite you to start a discussion about it on the imagej-devel
mailing list:

  http://imagej.net/Mailing_Lists

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-bugs/attachments/20150302/ae65d733/attachment.html>