Hi, I was going to start with moving the configuration stuff into the commons, but seeing as this is going to affect pretty much every last turbine project I thought I would ask for some input on the process of making such a change.
I can definitely move the classes but I think there should be some coordination as to making the changes in all the projects. Once this package is in the commons it won't happen again. But some changes akin to this might happen again while we are doing the final shuffle of code into the commons and the creation of our components in jakarta-turbine-component. After I move the classes can I have a couple volunteers to flip the turbine projects over to using the configuration package once it's in the commons? I will do turbine3. Then we can coordinate and say maybe freeze for half a day while we make our changes and try to get them in all at once so that everything will build. I can make all the changes but often when I do things like this I miss something and builds fail so I'm looking for a little backup this time. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
