You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by jv...@apache.org on 2002/02/13 17:51:03 UTC
cvs commit: jakarta-turbine-site/xdocs/common/status 15-feb-2002.xml
jvanzyl 02/02/13 08:51:03
Added: xdocs/common/status 15-feb-2002.xml
Log:
- preparing for friday's status report
eric do you think you could summarize what's been going on with
the security model. there's an entry for it, if you could expand
on what's going on that would be great.
Revision Changes Path
1.1 jakarta-turbine-site/xdocs/common/status/15-feb-2002.xml
Index: 15-feb-2002.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine 3</title>
<author email="jason@zenplex.com">Jason van Zyl</author>
</properties>
<body>
<section name="Weekly Status Report: 15 Feb 2002">
<p>
</p>
</section>
<section name="New Committers">
<p>
James Taylor was added as a new committer this week. James has been
working on the Pipeline, has added some JGenerator renderers which
is very cool, and generally helping out all over the place. Welcome
James!
</p>
</section>
<section name="Integration of the decoupled Torque in the TDK">
<p>
Martin has the decoupled Torque working with Turbine 2.x so he
is now working on integrating this work into the TDK. We are going
to officially deprecate the use of the coupled Torque, and when
we refer to Torque from now on we mean the decoupled Torque. The
Torque that exists in the 2.x tree is now officially dead.
</p>
</section>
<section name="Turbine Project Build System">
<p>
Jason has been working on a build system that can be used by all
Turbine projects. The goal is to have a single build.xml file that
can be used by all the builds. This is an effort to try and simplify
the maintenance overhead in all our projects now that we have decoupled
everything. We are going to move toward builds for each component in
Stratum and builds for each service in Fulcrum.
</p>
</section>
<section name="Commons Logging">
<p>
Aaron starting adding switching the logging in JCS over to log4j
and James suggested using the Commons Logging API so this is the
route that we will probably go in order to give our users flexibility.
</p>
</section>
<section name="Security Model">
<p>
Eric could you summarize what's going on here possibly.
</p>
</section>
<section name="RunData Reworking">
<p>
Explain the roadblock and maybe I can get some ideas from the group.
</p>
</section>
</body>
</document>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>