Short report about Turbine 2.4 porting progress

I'll try to describe my progress and issues, which occurs during porting.

1. After alternating dependencies there was about 2500 errors, which
prevents compilation. I decide to rapidly remove it at all and after
polish this replacements. Big thanks to Eric Pough, who make great job
on porting old scarab (i think it was a 0.20) to t2.4. All fatal
errors which prevents compilation was removed.
2. There are many rearrangement in little utility methods and classes
(like moving getRealPath and getApplicationRoot into Turbine class).
Many of this rearrangement was found after creating a stub (almost all
my debatable changes i mark with TODO or leave auto generated Eclipse
TODO), and need complete review after finishing first stage.
3. Next major problem is in Security service. In Turbine 3.0 there was
no complete API. It was wrote with scarab. But 2.4 has an interface.
At now i try to adapt ScarabUserManager (and other managers) to
corresponds this API. Security Service is main big difference which
was received with 2.4.
4. Next big problem was with Torque Security and Schedule service
implementation (in T2.4 torque dependency was removed). To compile
this i had to change schema (for using type of fields objects, not
primitives), and change target JVM to 1.5 to allow implicit casting,
also i replace torque dependency to 3.3, because by default there was
a 3.0 version used. This is not good because its Turbine code. But
this implementation looks like outdated bacause it's not compilable by
default (missing torque properties in project.properties).
5. Another problem occurs with intake. Situation like with Security
service (intake was developed in scarab). With our old xml conf intake
cannot init. There are some definitions, which produces errors. Like
N-prefixed (NPassword, etc) in Register form. Group ConditionEdit. If
anybody know how it works in old version, please let me know. Also i
replace NumberKey with BigDecimal (NumberKey omitted in
fulcrum-intake). Parameters (@SOME_NAME@) are not supported now.

That's all what i remember now. If i remeber something new i'll write again.