[ImageJ-devel] [fiji-devel] imglib coding style
ctrueden at wisc.edu
Wed Apr 14 17:02:20 CDT 2010
I completely agree that we should not require Eclipse as an IDE for Fiji or
ImageJ developers. No way, no how. :-)
Rather, my idea was to setup Eclipse on the server for use as a post-commit
It is possible to invoke certain Eclipse features from the command line,
such as the code formatter:
I have also been looking at Maven and it is capable of running many reports
(e.g., code coverage analysis) as part of its project web site generation.
With a continuous integration system such as Hudson in place, we can
leverage this functionality to provide a lot of feedback to the community on
a regular basis about the health of the project.
On Wed, Apr 14, 2010 at 4:48 PM, Johannes Schindelin <
Johannes.Schindelin at gmx.de> wrote:
> On Wed, 14 Apr 2010, Curtis Rueden wrote:
> > I agree that we should pay attention to the coding style of imglib,
> > ImageJ and related Fiji projects. My current plan for ImageJ is to use
> > Eclipse, since it allows you to define source code formatting
> > conventions and apply them. I believe you can also export the rules as
> > XML so that we can commit them to the git repository. Eventually we
> > could even have a post-commit hook to take care of it.
> I tried to avoid requiring Eclipse, but I won't fight the tide.
> You received this message because you are subscribed to the Google Groups
> "Fiji-devel" group.
> To post to this group, send email to fiji-devel at googlegroups.com.
> To unsubscribe from this group, send email to
> fiji-devel+unsubscribe at googlegroups.com<fiji-devel%2Bunsubscribe at googlegroups.com>
> For more options, visit this group at
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ImageJ-devel