[
https://issues.apache.org/jira/browse/OPENJPA-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714137#comment-13714137
]
Rick Curtis commented on OPENJPA-2410:
--------------------------------------
For some reason the changes I've made so far doesn't run correctly on *nix, and
also has problems when running on Maven 3.0+.
Unfortunately my linux machine is having problems right now so I can't get a
full build to complete... I'm going to try one more commit this evening to try
to get things *mostly* working and try to find some time later this weekend to
get things properly cleaned up.
Sorry for anyone that isn't able to build due to this little fiasco.
> Build time detection of System.out/err.print(ln) in source files
> ----------------------------------------------------------------
>
> Key: OPENJPA-2410
> URL: https://issues.apache.org/jira/browse/OPENJPA-2410
> Project: OpenJPA
> Issue Type: Improvement
> Components: build / infrastructure
> Affects Versions: 2.3.0
> Reporter: Di Wu Lau
> Assignee: Rick Curtis
> Priority: Minor
> Fix For: 2.3.0
>
> Attachments: OPENJPA-2410.patch, OPENJPA-2410r1.patch,
> OPENJPA-2410r2.patch
>
>
> Source files may have inadvertent System.out/err.print statements left in
> source files on commit. Ideally we don't want any of these changes being
> checked in and a large majority of the time logging facilities should be
> utilized. That being said, there are a number of cases where we don't have
> access to a logger and must use System.out/err.
> This JIRA will be used to update our checkstyle to scan for unwanted print
> statements, and fail the build when/if they are encountered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
