A quick status update on working towards 2.4.
I have finished integrating some more of the various Fulcrum components,
including Crypto, Cache, and Mimetype. At this point, all that needs to be
integrated are Factory and Pool. I rejiggered the build structure a bit,
but the end result should continue to be backwards compatable. I added a
new toplevel directory "extensions" where various non core extensions to
Turbine could go. I am thinking that code that brings in a large number of
external dependencies or bulks up the app server extensivly or requires
complex build steps would go here. If the code to be added was a component
that is generic, then it would go in Fulcrum.
In the extensions directory are now the Maven plugin for Turbine and the
Torque backed implementations for Schedule and Security. I added an
interface to the Turbine core "JobEntry". This is implemented by the Torque
backed interface. What this allows is the API for Schedule and Security to
be in the Turbine
core, while the implementations that require Torque codegeneration magic are
in the extensions/torque directory. This allows us to move out of the
Turbine core compilation process all of the Torque plugin stuff. Which
should lead to much simpler builds and should allow new developers to come
up to speed with Turbine much faster! Also hopefully reduce all those
"Can't build due to plugin" emails!
Lastly, it allows other backends to be supplied for the scheduler service as
well.
What I see left for 2.4!
* Finish integrating Fulrum Pool and Factory components.
* Implement a MerlinComponentService to replace the current Excalibur based
AvalonComponentService.
* Update Fulcrum components to work with Merlin.
* Deprecate Turbine Security in favor of Fulcrum Security.
* This requires the LDAP provider from Turbine to be moved over.
* Also requires the Torque generation of code to be done in Fulcrum
Security. This should probably
be done as a subproject of Fulcrum Security so as not to impact the
entire build...
* Properly document all the changes required. Basically
TurbineResources.properties is going to be gutted.
I would appreciate it if someone could test out the current build. I added
a Howto Build Turbine page to help get you started. Basically it leverages
the Multiproject plugin for Maven to do the build.
If you check out the site docs
(http://jakarta.apache.org/turbine/turbine-2.4/index.html), you will see the
new Jcoverage and Simian reports!
Comments?
Eric Pugh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
