Except developers I do not expect anybody to create any implementation.
However, even in this case "it is not nice" to break other applications
if not really really necessary.
I personally would not mind to have the configuration as java object, it
would be probably less confusion for the average developer. Question
like "what keys to use to do X and Y" would probably dissapear(maybe :)
) since the configuration will be pure Java objects(with comments).
Anyway, Velocity should not depend on 2 external libraries just to be
able to setup the configuration. The core should not depend on anything
else except J2SE.
On 11/30/2010 09:51 AM, Antonio Petrelli wrote:
2010/11/30 Adrian Tarau<[email protected]>:
Since it is an interface adding getUserDirectives2 will break my
application. That's the downside with interfaces, if you add stuff things
will not compile anymore and everybody is forced to adjust their code - not
a big deal in this case, but ...
Wait a moment, with the exception of Velocity developers, is anyone
intentioned on creating configuration implementations?
If not, I think it's not a problem.
If yes, you will notice that, after upgrading, you will have a
compilation failure, and it's a *good* thing, since it lets you know
something new happened.
Anyway, a "support" (implementation of an interface with all methods
doing nothing) protects against this kind of compilation problems.
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
