You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by vg...@apache.org on 2007/10/22 20:14:21 UTC
svn commit: r587176 - /cocoon/trunk/core/cocoon-core/src/changes/changes.xml
Author: vgritsenko
Date: Mon Oct 22 11:14:20 2007
New Revision: 587176
URL: http://svn.apache.org/viewvc?rev=587176&view=rev
Log:
2.2 m3 is released
Modified:
cocoon/trunk/core/cocoon-core/src/changes/changes.xml
Modified: cocoon/trunk/core/cocoon-core/src/changes/changes.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/core/cocoon-core/src/changes/changes.xml?rev=587176&r1=587175&r2=587176&view=diff
==============================================================================
--- cocoon/trunk/core/cocoon-core/src/changes/changes.xml (original)
+++ cocoon/trunk/core/cocoon-core/src/changes/changes.xml Mon Oct 22 11:14:20 2007
@@ -17,28 +17,32 @@
specific language governing permissions and limitations
under the License.
-->
-<!--+
- | @version $Id$
- +-->
+
+<!--
+ - @version $Id$
+ -->
<document>
<properties>
<title>Changes Cocoon Core</title>
</properties>
+
<body>
- <release version="2.2.0-M3-SNAPSHOT" date="2007-00-00" description="unreleased">
+ <release version="2.2.0-M3-SNAPSHOT" date="2007-03-02" description="released">
<action dev="dfagerstrom" type="update">
Refactoring to make the pipelines usable outside the tree processor:
- (1) The source resolver in AbstractProcessingPipeline is looked up from the service
- manager that is inserted with the setProcessorManager instead of from the
- EnvironmentHelper.getCurrentProccessor method. After having traced the call
- sequence it seem to be equivalent and from testing it seem to work.
- (2) Changed the return type SitemapErrorHandler.prepareErrorHandler to Processing
- pipeline which is the same as it in Cocoon 2.1.x. Before the pipeline was embedded
- in a descriptor object. The only use for that in the pipeline context was that
- it was used for having a refernce to the container that created the pipeline and
- could use that for releasing the pipeline. But in the Spring Avalon implementation
- the release method is a noop.
- </action>
+ <ul>
+ <li>The source resolver in AbstractProcessingPipeline is looked up from the service
+ manager that is inserted with the setProcessorManager instead of from the
+ EnvironmentHelper.getCurrentProccessor method. After having traced the call
+ sequence it seem to be equivalent and from testing it seem to work.</li>
+ <li>Changed the return type SitemapErrorHandler.prepareErrorHandler to Processing
+ pipeline which is the same as it in Cocoon 2.1.x. Before the pipeline was embedded
+ in a descriptor object. The only use for that in the pipeline context was that
+ it was used for having a refernce to the container that created the pipeline and
+ could use that for releasing the pipeline. But in the Spring Avalon implementation
+ the release method is a noop.</li>
+ </ul>
+ </action>
</release>
<release version="2.2.0-M2" date="2006-12-00" description="pending">
<action dev="cziegeler" type="update">