About the issues...
Scheduler: Could we not solve this as you did with the security service and keep the 2.3.3 implementation? Later, if there is time and resources we could implement a standalone service. I really think a complete working package is worth much more than splitting up the parts the right way. Another thing is that for projects using turbine 2.3.3, the move to T4 is less painful if they do not need to change all the services at one time. The migration will probably be easier if it's done one step at a time. I'm not sure if T4-M1 is meant for production environments though.. TurbineServiceProvider: Actually I'm currently trying to figure out how to get hold of serveices outside of Servicable objects. I have not found any counterpart to TurbineServices.getInstance().getService(). Maven2 build: Seems to work with tests today. or am I missing something? /Ludwig From: Thomas Vandahl [mailto:[email protected]] Sent: den 18 januari 2011 18:28 To: Turbine Developers List Subject: Re: First (real) commit Looks good to me. In http://markmail.org/message/zp6ihkkwe72d263y I wrote something about what I see missing until we can get a 4.0 milestone out. I addressed the security issue by copying the 2.3.3 code over. The rest is still pending. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] _____ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1191 / Virus Database: 1435/3388 - Release Date: 01/18/11
