I believe you got a more reasonable error message in 5.2. In 5.3 you may get an error if both the fields have @Property, due to a name collision on the getter/setter method names. Instead, Tapestry should fail early explaining that both the component and (the identified base class) define the same parameter name.
|Field||Original Value||New Value|
|Summary||Tapestry 5.3 allows a subcomponent to defined a parameter with the same name as a base component||Tapestry 5.3 allows a subcomponent to define a parameter with the same name as a base component|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Fix Version/s||5.3 [ 12316024 ]|
|Resolution||Fixed [ 1 ]|