In both cases I would expect a hard exception instead of a soft warning.
There’s already enough magic going on in the background.
Best,
Rafael
On October 27, 2017 3:57:59 PM Dmitry Gusev wrote:
Hi Thiago,
I would expect this to throw an exception on application start.
I would also expec
On Fri, Oct 27, 2017 at 11:57 AM, Dmitry Gusev
wrote:
> Hi Thiago,
>
Hello, Dmitry!
> I would expect this to throw an exception on application start.
>
Thanks for your opinion! Even more for agreeing with me! :D
> I would also expected that `configuration.override` would fix this,
>
It wou
Hi Thiago,
I would expect this to throw an exception on application start.
I would also expected that `configuration.override` would fix this,
although it's not that clear what should happen if you're overriding a
contribution twice, say, in different modules.
Can we order the overrides somehow?
Hello!
I've just stumbled again at https://issues.apache.org/jira/browse/TAP5-1305,
which boiled down to Tapestry-IoC dropping a contribution to an ordered
configuration if there's another contribution with the same id. I fixed it
specifically for service decorators. For service configurations, it