You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pdfbox.apache.org by ms...@apache.org on 2017/03/17 11:11:32 UTC
pdfbox-docs git commit: PDFBOX-3330: minimal change to trigger
rebuild of the page because of layout issues
Repository: pdfbox-docs
Updated Branches:
refs/heads/master 0734a0a3d -> 977224f9d
PDFBOX-3330: minimal change to trigger rebuild of the page because of layout issues
Project: http://git-wip-us.apache.org/repos/asf/pdfbox-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/pdfbox-docs/commit/977224f9
Tree: http://git-wip-us.apache.org/repos/asf/pdfbox-docs/tree/977224f9
Diff: http://git-wip-us.apache.org/repos/asf/pdfbox-docs/diff/977224f9
Branch: refs/heads/master
Commit: 977224f9d77b7e4a81f86f8690fadbe323fbd0e4
Parents: 0734a0a
Author: Maruan Sahyoun <sa...@fileaffairs.de>
Authored: Fri Mar 17 12:11:02 2017 +0100
Committer: Maruan Sahyoun <sa...@fileaffairs.de>
Committed: Fri Mar 17 12:11:02 2017 +0100
----------------------------------------------------------------------
content/codingconventions.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/pdfbox-docs/blob/977224f9/content/codingconventions.md
----------------------------------------------------------------------
diff --git a/content/codingconventions.md b/content/codingconventions.md
index f626234..b7347f5 100644
--- a/content/codingconventions.md
+++ b/content/codingconventions.md
@@ -22,7 +22,7 @@ title: Coding Conventions
# Coding Conventions
-Over the years the PDFBox project has come to adopt a number of coding conventions. These are not always followed in old code but new code should try to follow these rules where possible.
+Over the years the PDFBox project has come to adopt a number of coding conventions. These are not always followed in old code but new code should follow these rules where possible.
### Formatting
@@ -112,7 +112,7 @@ Over the years the PDFBox project has come to adopt a number of coding conventio
- Don't expose implementation details unless there is a clear need: allowing subclassing means that the behaviour of protected methods becomes part of the contract of the public AP.
- Avoid unnecesary abstraction. While you're encouraged to avoid brittle designs, it's unlikey that an API designed for "future use" will have the correct API without any code which actually uses it.
-
+
### Example
Here's an example of PDFBox's formatting style:
@@ -139,9 +139,9 @@ public class Foo extends Bar
## Eclipse Formatter
-Eclipse users may download this preferences file: pdfbox-eclipse-formatter.xml and import this into Eclipse.
+Eclipse users may download this preferences file: pdfbox-eclipse-formatter.xml and import this into Eclipse.
(Window->Preferences, go to Java->Code Style->Formatter and click "Import...").
Once you have done this you can reformat your code by using Source->Format (Ctrl+Shift+F).
-Also note that Eclipse will automatically format your import statements appropriately when
+Also note that Eclipse will automatically format your import statements appropriately when
you invoke Source -> Organize Imports (Ctrl+Shift+O).