Rainer W.

For an plugin architecture OSGi would be nice. Supports versioning, and with bndtools live reloading comes out of the box. But not sure if this suites the idea of an...

Do you really need a plugin architecture inside JBake-core ? At the moment JBake consists of two things: - jbake-core * The actuall business logic to generate pages. - jbake-cli...

- passing this into a rule is ugly, but i could live with that - Not having the actual method instance could be a problem with multiple overloadings - I...

While rewriting i found that the description.getAnnotations() only finds Annotations from the current testMethod, but none from overwritten methods. This is actually a feature i need. https://gist.github.com/1309806 So description.getAnnotations() should...

Actually, passing in $this, is really ugly. This breaks all existing projects, not only the rules. I have actually to change all projects and bloat up the constructor. Isn't there...

This would solve the problem, but now you have two interfaces doing the same thing. So one is just cluttering your API. Which one should you use for new rules?...

I completely agree, having a distinct interface for @ClassRule and @Rule is a good thing. But still you have to explain why in MethodRule you have no Descriptor parameter (Not...

To fix this this i would recommend: https://gist.github.com/2358589 - create a RuleStatement as replacement for MethodRule/TestRule The actual apply() method now has only a "RuleParameter" - create two sub-interfaces of...

@dsaff did you play with the idea?

Sorry, for the late reply, here my comments to the proposal: The idea of rules solving different problems look's nice, but i'm not sure if this should be solve by...