I've prepared the artifacts for the release of our four subprojects:
Cocoon Servlet-Service Framework Impl 1.1.0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The most important change is that it doesn't depend on the Cocoon source
resolver any more. Custom protocols (e.g. block-context) can still be
used by registering them with JNet.
Cocoon Spring Configurator 2.0.0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A major release is necessary because the block deployment functionality
was rewritten and moved into the separate Block-Deployment module.
Apart from this there have been some minor bug fixes and improvements.
Cocoon JNet 1.0.0
~~~~~~~~~~~~~~~~~
Cocoon JNet allows the dynamic registration of URLStreamHandler
factories with your JVM. That's a feature that isn't supported by Java
itself.
This module was donated to the Apache Commons project and will hopefully
be released there sooner or later.
That's the first release of this module.
Cocoon Block-Deployment 1.0.0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Block-Deployment module provides a Java servlet context listener,
that unpacks all blocks into the temp directory of the current servlet
context.
Previously this functionality was part of the Spring Configurator but
was considered to be too Cocoon specific.
That's the first release of this module.
- o -
Additionally I've prepared the artifacts for the release of the
Cocoon Maven Plugin 1.0.0-M3
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The only difference to M2 is that it was compiled with Spring 2.5.5
because M2 causes some wired exceptions when it is used with Spring >2.5.2.
As always, the release of the Cocoon Maven Plugin also makes the release
of the cocoon-rcl-webapp-wrapper and cocoon-rcl-spring-reloader necessary.
Cocoon Parent POM - Version 7 & Cocoon Tools Modules - Version 7
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In order to use the most recent dependency and plugin versions in the
subprojects and the Maven plugin, I had to create a new release of the
Cocoon Parent POM and the Cocoon Tools Modules.
- o -
Currently the proposed artifacts can only be tested either with latest
trunk or Corona.
For that purpose add a 'cocoon-staging' profile to your Maven settings.xml:
<profile>
<id>cocoon-staging</id>
<repositories>
<repository>
<id>cocoon.staging</id>
<name>Cocoon staging repository</name>
<url>http://people.apache.org/builds/cocoon</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>cocoon.staging</id>
<name>Cocoon staging repository</name>
<url>http://people.apache.org/builds/cocoon</url>
</pluginRepository>
</pluginRepositories>
</profile>
and use the proposed artifacts instead of SNAPSHOT versions.
- o -
You can find the staged files for all modules (sources, binaries,
javadocs, checksums, gpg signatures) at
- http://people.apache.org/builds/cocoon/
(Maven 2 repo)
- http://people.apache.org/~reinhard/cocoon-staging/
(Standard release artifacts)
SVN tags of all these artifacts can be found at
http://svn.apache.org/repos/asf/cocoon/tags/.
This majority vote stays open for 72 hours.
Please cast your votes.
Here is my +1 (after successfully testing with Cocoon trunk and Corona).
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member [EMAIL PROTECTED]
________________________________________________________________________
