Martin Poeschl <[EMAIL PROTECTED]> writes: > Henning P. Schmiedehausen wrote: > > >Hi, > > > >as one of the first Post-2.2 Things on my ToDo list is the killing of > >the TurbineResources Service and replacing it with > >commons-configuration. > > > >I have our internal Turbine 2.x tree running with this for about a > >year now and it works very well (the side effect of being able to use > >XML configuration files in the future not even mentioned. :-) ) > > > >To be able to make the transition clear, we internally use only > >Turbine.properties as configuration file and no longer > >"TurbineResources.properties" which was IMHO a misnomer from the > >start. > > > >Any objection to renaming this configuration file (and clearly > >mentioning this in the post 2.2 development as a "might break > >applications" change) when moving to commons-configuration? It will > >also bring the Names in line with Fulcrum.properties and > >Torque.properties? > > > >I'm obviously +1 on this. > > > +1 > > if it is possibe mark the TurbineResources Service deprecated and > change it to use the new property file (so users just need to rename > the file but don't need to change their code .. or maybe we cann look > for both filenames??) > > > i just want to make the next version as backawards compatible as possible
As Martin says, +1. -- Daniel Rall <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
