You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Dave Thompson (JIRA)" <ji...@apache.org> on 2018/10/05 16:47:00 UTC
[jira] [Closed] (DAFFODIL-1980) suppressWarnings vs.
suppressSchemaDefinitionWarnings in config files
[ https://issues.apache.org/jira/browse/DAFFODIL-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Thompson closed DAFFODIL-1980.
-----------------------------------
Pulled latest updates from incubator-daffodil repository which included specified commit, 2612ad8da23a70ebefd82f351ad83db8d8e89022.
Verified daffodil builds and executes all sbt tests successfully.
Verified changes specified in this JIRA ticket.
All nightly tests also executed successfully.
> suppressWarnings vs. suppressSchemaDefinitionWarnings in config files
> ---------------------------------------------------------------------
>
> Key: DAFFODIL-1980
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1980
> Project: Daffodil
> Issue Type: Bug
> Components: API, Front End
> Affects Versions: 2.1.0
> Reporter: Michael Beckerle
> Assignee: Dave Thompson
> Priority: Major
> Fix For: 2.2.0
>
>
> The code isn't consistent about whether the name for suppressing warnings is "suppressWarnings" or "suppressSchemaDefinitionWarnings". This made it impossible to use the feature.
> Change to suppressSchemaDefinitionWarnings since that is the name of the actual tunable.
> Or if we like suppressWarnings better we should change the name uniformly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)