You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/08/22 06:48:23 UTC
[jira] [Closed] (TAP5-1645) Tapestry should validate that abstract
classes only appear in the .base sub-package, not in .components, .mixins
or .pages
[ https://issues.apache.org/jira/browse/TAP5-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-1645.
--------------------------------
Resolution: Incomplete
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.4.1 or newer), feel free to provide the necessary information and reopen.
> Tapestry should validate that abstract classes only appear in the .base sub-package, not in .components, .mixins or .pages
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1645
> URL: https://issues.apache.org/jira/browse/TAP5-1645
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Labels: bulk-close-candidate
>
> Tapestry has a .base sub-package for base classes for components; although a non-abstract class may or may not be a base class, an abstract class by definition is. Tapestry should treat this as an error (but should include a compatibility setting to turn off the check).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)