Historically we have implemented all sorts of stuff into surefire, without giving the user appropriate hooks to control the behaviour for herself. One such very simple example is an extensibility point to allow the user to run tests in a specific order they can decide themselves. Another is opening "hooks" that would allow custom remoting/forking. There "used" to be quite a lot of these possible features, but over the years a lot of them have just been implemented/added, increasing the footprint (and feature/bug footprint too !)
So we have been discussing (in email) if we could modularize the plugin in such a way that default behaviour is cleanly replacable/supplementable via user-supplied hooks. So far we've just been throwing around ideas, and Tibor just brought this discussion to the mailing list. I am not very happy that the plugin is such a monolith. And the way we are closed for user extensions means we'll continue growing. And it's not just surefire. Surefire is a bit special in the context that we have a scope that "belongs" to surefire. We can pick up stuff from test scope and run it as part of the plugin. Ideally I would really like to think extensibility in this manner for all kinds of plugins. I'd really like somewhere I can just tack in my java8 lambda/or interface implementation and have maven pick it up.... Kristian 2015-01-13 17:34 GMT+01:00 Igor Fedorenko <i...@ifedorenko.com>: > I think my question was not clear. I do not understand the problem you > are trying to solve, i.e. user and/or plugin developer usecases that are > not (well) supported with the current APIs. This is why I am asking for > some representative examples that highlight the problem. I do not > suggest or imply that I have an alternative solution or vision, I just > want to understand what you are trying to achieve with the new API. > > -- > Regards, > Igor > > > On 2015-01-13 10:50, Tibor Digana wrote: >> >> Igor, can we join our visions and design together regarding compiler and >> surefire ? >> I guess we need to write a list of requirements. Later we will find >> possible >> solutions for each + API. >> >> >> >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/Plugable-Softcoded-Customized-Maven-Plugins-tp5823365p5823378.html >> Sent from the Maven Developers mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
