Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Java Coding Style

Java Code shall be formatted according Code Conventions for the Java Programming Language by Sun Microsystems, Inc.
Additional, indentations shall be done by (4)spaces, instead of tabs.

See Eclipse IDE Configuration on setting these standard in Eclipse.

Documentation of commitments in JIRA

Every commitment to the project CVS or SVN at Sourceforge should be associated with (at least) one entry in JIRA, by including the JIRA issue key in the commit comment. Reformatting of source code should be done by separate commits with a comment like 'pretty format'.

About resolving and closing issues in JIRA

The Assignee shall set the status of an Open issue to Resolved, after the commitment of the modification into the CVS or SVN at Sourceforge. Resolved issues shall be Closed by the Reporter. If the Assignee is also the Reporter of an issue, the issue may direct be Closed by the Assignee, skipping the Resolved status. (s.o. JIRA Default Workflow).

Java Version Compatibility

Unless previously decided and stated, dcm4che sub-projects shall maintain compatibility with JDK 5.0. The exception is dcm4che14, which remains at a 1.4 compatibility for now. dcm4che2, dcm4chee 2.x. dcm4chee 3.x and Xero are able to use JDK 5. Read this thread in the forums for more discussion.

Eclipse IDE Configuration

If you're using Eclipse to work on dcm4che, follow the instructions on Eclipse IDE Configuration to make sure you're on par with the standards.

  • No labels