Date: Thu, 28 Mar 2024 16:15:36 +0000 (UTC) Message-ID: <1091664307.25.1711642536594@ea0904977630> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_24_959047749.1711642536594" ------=_Part_24_959047749.1711642536594 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Java Code shall be formatted according Code Con=
ventions 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 sett= ing these standard in Eclipse.
Every commitment to the SVN source code repository on Sourceforge should=
be associated with (at least) one entry in JIRA, by including th=
e JIRA issue key in the commit comment. Reformatting of source code should =
be done by separate commits with a comment like 'pretty format
=
'. There are a few reasons for doing this:
The Assignee shall set the status of an Open i= ssue to Resolved, after the commitment of the= modification into the CVS or SVN at Sourceforge. Resolved iss= ues shall be Closed by the Reporter. If the Assignee is also the Reporter of an issue, the issue m= ay direct be Closed by the Assignee, skipping the= Resolved status. (s.o. JIRA Default Workflow).
Unless previously decided and stated, dcm4che sub-projects shall maintai= n compatibility with JDK 5.0. The exception is dcm4che14, which remains at = a 1.4 compatibility for now. dcm4che2, dcm4chee 2.x and dcm4chee 3.x use JD= K 5+. Read this= thread in the forums for more discussion.
If you're using Eclipse to work on dcm4che, follow the instructions on <= a href=3D"/wiki/spaces/ee2/pages/2556017/Eclipse+IDE+Configuration" data-li= nked-resource-id=3D"2556017" data-linked-resource-version=3D"12" data-linke= d-resource-type=3D"page">Eclipse IDE Configuration to make sure yo= u're on par with the standards.