http://imagej.273.s1.nabble.com/Plugin-for-compiling-all-plugins-tp5003613p5003636.html
Sure, give it a try. Just make sure the class name has an underscore in
that case. It will be in a submenu named after the package.
> AH, I was not aware that this was possible! Can plugins with
> packages also be used if the code is not contained in a JAR file? Can they
> be re-compiled on demand, re-loaded and executed?
>
> --Wilhelm
>
>
> ------------------------------
> *From:*
[hidden email] [
[hidden email]] On Behalf Of
> Curtis Rueden [
[hidden email]]
> *Sent:* Tuesday, June 25, 2013 20:52
> *To:* Burger Wilhelm
> *Cc:*
[hidden email]
>
> *Subject:* Re: Plugin for compiling all plugins?
>
> Hi Wilhelm,
>
> > ImageJ plugins are not supposed to reside in packages
>
> Why not? As long as you have a plugins.config defining which classes are
> plugins, they can live in packages, and they do not need an underscore in
> the name. Perhaps that would make your life easier?
>
> Regards,
> Curtis
>
>
> On Tue, Jun 25, 2013 at 12:50 PM, Burger Wilhelm <
>
[hidden email]> wrote:
>
>> Hello Curtis,
>>
>> yes, the assumption is that I have a set of plugin source-files (.java)
>> placed in multiple folders inside the 'plugins' folder. I thought of a
>> command "Compile all..." command (similar to "Compile and run..") that
>> simply compiles all these source files but does not run anything. Of course
>> I guess one could also run javac from the command line.
>>
>> My IDE (Eclipse) is actually part of the problem. I wanted to distribute
>> a structured set of plugins with .java and .class files side-by-side. My
>> Eclipse project is already rooted at the ImageJ's plugins folder, each
>> inner folder in 'plugins' is a source folder which is its own output folder
>> - thereby .java and compiled .class files come to lie together, just as I
>> want. However, since ImageJ plugins are not supposed to reside in packages
>> - Eclipse cannot export these source folders to a JAR file other than as a
>> flat container (removing all sub-folders). So I thought I let Eclipse only
>> generate the source tree and then run the compiler over it with that
>> intended ImageJ command. Weird idea?
>>
>> Thanks much for the hints, I think I'll try the command line approach
>> now...
>>
>> --Wilhelm
>>
>> ________________________________________
>> From: ImageJ Interest Group [
[hidden email]] On Behalf Of Curtis
>> Rueden [
[hidden email]]
>> Sent: Tuesday, June 25, 2013 17:33
>> To:
[hidden email]
>> Subject: Re: Plugin for compiling all plugins?
>>
>> Hi Wilhelm,
>>
>> > does anyone know of way to (re-)compile all other plugins within the
>> > <ImageJ>/plugins/ directory? Any hints appreciated...
>>
>> Presumably you have the source code for all such plugins in the plugins
>> folder?
>>
>> You say "all other plugins" -- does that mean you want to recompile the
>> other plugins from within a plugin of your own, at runtime? Or would it be
>> sufficient to use something like "javac -cp '../jars/*' *.java" on the
>> command line from the plugins folder?
>>
>> Regards,
>> Curtis
>>
>> P.S. If externally recompiling is sufficient, but you don't like the
>> command line, you could create an IDE project around your ImageJ folder,
>> setting your plugins folder as the source folder, and all JARs in the jars
>> folder as dependencies.
>>
>>
>> On Tue, Jun 25, 2013 at 1:52 AM, Burger Wilhelm <
>>
[hidden email]> wrote:
>>
>> > Hello group,
>> >
>> > does anyone know of way to (re-)compile all other plugins within the
>> > <ImageJ>/plugins/ directory? Any hints appreciated...
>> >
>> > --Wilhelm
>> >
>> > --
>> > ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>> >
>>
>> --
>> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>>
>
>