Ticket #165 (closed task: fixed)

Opened 9 years ago

Last modified 7 years ago

Maven: better style checking procedure

Reported by: curtis Owned by: curtis
Priority: trivial Milestone: imagej2-b3-headless
Component: Build System Version:
Severity: non-issue Keywords:
Cc: Blocked By:
Blocking:

Description (last modified by curtis) (diff)

It would be good to have a common code style across the codebase. Maven's  checkstyle plugin has some predefined rulesets we could use, or we can create our own, and develop a set of Eclipse auto-formatting rules to match.

Change History

comment:1 Changed 9 years ago by curtis

  • Description modified (diff)

comment:2 Changed 9 years ago by curtis

  • Component changed from other to build

comment:3 Changed 9 years ago by curtis

  • Milestone changed from biweekly-2010: Sep-07 to Sep-17 to biweekly-2011: Jan-03 to Jan-14

comment:4 Changed 8 years ago by curtis

  • Milestone changed from biweekly-2011: Feb-14 to Feb-25 to imagej-2.0-release

comment:5 Changed 8 years ago by curtis

There are now Eclipse configuration files in the repository. The next step (eventually) would be to have a Maven target for checking for style violations.

comment:6 Changed 7 years ago by curtis

  • Status changed from new to closed
  • Resolution set to fixed

I recently added the ability to call the Eclipse code formatter from Maven via the maven-java-formatter-plugin; see c095814d. This is an incomplete solution, but doing more than that right now would be more trouble than it's worth.

comment:7 Changed 7 years ago by curtis

  • Milestone changed from imagej-2.0.0 to imagej-2.0.0-beta3
Note: See TracTickets for help on using tickets.