[jira] Resolved: (WICKET-761) Disable line-precise exceptions for component use check

["Martijn Dashorst (JIRA)" <ji...@apache.org>]

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

Martijn Dashorst resolved WICKET-761.
-------------------------------------

    Resolution: Fixed

Made the line precise error reporting optional and split into two: one for added and one for new components, default off for normal usage (until we come up with application profiles). Maybe enable it explicitly in quickstarts where it is easy to remove the two lines.

> Disable line-precise exceptions for component use check
> -------------------------------------------------------
>
>                 Key: WICKET-761
>                 URL: https://issues.apache.org/jira/browse/WICKET-761
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3.0-beta1, 1.3.0-beta2
>            Reporter: Igor Vaynberg
>            Assignee: Martijn Dashorst
>             Fix For: 1.3.0-beta3
>
>
> vote here:
> http://www.nabble.com/-VOTE--disable-line-precise-error-reporting-by-default-tf4037146.html#a11469624
> while looking in the code i noticed that line-precise information is collected under the same setting as component-use-check. i think the exception part should be factored out into a separate setting. component use check is still very valuable without line-precise information and has no perceptible slow down like the line-precise exceptions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.