[jira] [Updated] (TAP5-1645) Tapestry should validate that abstract classes only appear in the .base sub-package, not in .components, .mixins or .pages

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1645:
---------------------------------
    Labels: bulk-close-candidate  (was: )

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> 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)