[
https://issues.apache.org/jira/browse/PDFBOX-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983145#comment-15983145
]
Tilman Hausherr commented on PDFBOX-2852:
-----------------------------------------
I'm not really doing it fully manually. I use netbeans. It has an "inspect and
transform" feature which is probably similar to what you mention. However I
still review every change, because sometimes formatting is bad, comments are
lost, sometimes the refactored code is "paranoid" (checks for null on an object
that is never null), and in one recent case this weekend, code logic was
changed. I'm mostly done, and it isn't really as much work as it seems - most
of it was done while watching TV or netflix on a second screen.
> Improve code quality (2)
> ------------------------
>
> Key: PDFBOX-2852
> URL: https://issues.apache.org/jira/browse/PDFBOX-2852
> Project: PDFBox
> Issue Type: Task
> Affects Versions: 2.0.0
> Reporter: Tilman Hausherr
> Attachments: explicit_array_creation.patch, fix_javadoc.patch,
> foreach2.patch, foreach.patch, generic_type_arguments.patch, noarray.patch,
> PDNameTreeNode.java.patch, semicolon.patch, StringBuffer.patch,
> stringbuilder.patch, unnecessary_type_casting.patch, unused_imports.patch,
> usestatic.patch, winansiencoding2.patch, winansiencoding.patch,
> XMPSchema.java.patch
>
>
> This is a longterm issue for the task to improve code quality, by using the
> [SonarQube
> report|https://analysis.apache.org/dashboard/index/org.apache.pdfbox:pdfbox-reactor],
> hints in different IDEs, the FindBugs tool and other code quality tools.
> This is a follow-up of PDFBOX-2576, which was getting too long.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
