Ticket #165 (closed task: fixed)
Opened 2010-08-23T11:56:34-05:00
Last modified 2012-06-08T12:05:01-05:00
Maven: better style checking procedure
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | trivial | Milestone: |
|
| Component: | Build System | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: |
Description (last modified by curtis)
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:3 Changed 2010-09-15T12:05:57-05:00 by curtis
- Milestone changed from biweekly-2010: Sep-07 to Sep-17 to biweekly-2011: Jan-03 to Jan-14
comment:4 Changed 2011-02-15T10:40:38-06:00 by curtis
- Milestone changed from biweekly-2011: Feb-14 to Feb-25 to imagej-2.0-release
comment:5 Changed 2011-03-13T20:30:39-05:00 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 2012-06-08T12:04:46-05:00 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 2012-06-08T12:05:01-05:00 by curtis
- Milestone changed from imagej-2.0.0 to imagej-2.0.0-beta3