apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chandni Singh (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (APEXMALHAR-2043) Update checkstyle plugin declaration to use apex-codestyle-config artifact
Date Tue, 05 Apr 2016 00:34:25 GMT

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

Chandni Singh reopened APEXMALHAR-2043:

In Malhar we were enabling/disabling logging to console with the property `consoleOutput`.
When this property is enabled, it spits out Errors and warnings as well.

Now that we are using the apex-checks.xml from ApexCore where line length violations are treated
as warnings, Malhar will print out all these warnings for new modules.

Instead of `consoleOutput`, we should be using `logViolationsToConsole` which only spits out
errors (not warnings).

> Update checkstyle plugin declaration to use apex-codestyle-config artifact
> --------------------------------------------------------------------------
>                 Key: APEXMALHAR-2043
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2043
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>            Reporter: Chandni Singh
>            Assignee: Chandni Singh
>             Fix For: 3.4.0
> We have created apex-codestyle-config which externalizes checkstyle configurations.
> Malhar has a copy of apex_checks.xml and checkstyle-suppressions.xml. These can be removed
by adding dependency to apex-codestyle-config in the checkstyle plugin.

This message was sent by Atlassian JIRA

View raw message