[jira] [Updated] (OFBIZ-12061) Comment out HideUtilityClassConstructor in checkstyle.xml

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Le Roux updated OFBIZ-12061:
------------------------------------
    Sprint: OFBiz Community Day (Nov 2020)

> Comment out HideUtilityClassConstructor in checkstyle.xml
> ---------------------------------------------------------
>
>                 Key: OFBIZ-12061
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12061
>             Project: OFBiz
>          Issue Type: Improvement
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Major
>
> Currently Checkstyle returns 222 occurrences of the message "Utility classes should not have a public or default constructor."
> This is due to https://checkstyle.sourceforge.io/config_design.html#HideUtilityClassConstructor
> I don't think we need to follow the "prevents calls from subclass" suggestion  there.
> I rather suggest to comment out the related class in checkstyle.xml:
> bq. ie <!-- <module name="HideUtilityClassConstructor"/> -->
> Then should remain only 280 errors and hopefully most will be easy to fix. At least they will be easier to spot...

--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[aylarose495]

That update in Jira shows how important proper configuration and tracking tools are when managing performance and system checks. Just like development teams rely on precise metrics for code quality, gamers use Faceit Finder to analyze ELO, K/D ratios, and detect smurfs or cheaters with accurate data. Both cases highlight how the right tools bring clarity, improve performance, and ensure fair results.

[Anderson]

This approach makes sense, especially if the goal is to reduce noise and focus on more actionable Checkstyle issues. Commenting out HideUtilityClassConstructor should help surface errors that are easier to prioritize and resolve. For a simple reference point on keeping things streamlined and accessible, check out Futbol Libre TV.

[mark771]

This update is a practical step toward improving developer productivity. Reducing excessive Checkstyle warnings helps teams focus on real, high-impact issues instead of getting buried in noise. Clear configuration and smarter tooling always lead to better code quality and smoother collaboration—similar to how communities optimize workflows in other spaces, even niche ones like Roblox Mod APK development, where clarity and structure also matter for long-term maintenance.