Incorrect behaviour when both <rules/> and <conversion/> are specified

Description

When both <rules/> and <conversion/> are specified in a contribution schema, Gaderian won't report any error message. It looks like it'll put the class from <conversion/> on top of the stack and then execute the rules, which, in the end, results in a NoSuchMethodException: addElement at org.apache.hivemind.schema.rules.InvokeParentRule.findMethod(InvokeParentRule.java:127).

Environment

None

Status

Assignee

Raffael Herzog

Reporter

Raffael Herzog

Labels

None

Components

Priority

Minor
Configure