Jorg Heymans wrote:
Reinhard Poetz wrote:
Jorg,
IIRC it was you who worked on providing proper Avalon and Excalibur
artifacts to central. What's the status of your work?
The status can be found here:
http://thread.gmane.org/gmane.comp.apache.excalibur.devel/1980/focus=1980
I figured Cocoon was fully moving away from avalon/excalibur and thus
lost interest a bit in doing the release.
That's our long term goal and we maybe reach it with 3.0. 2.2 will definitly use
Avalon/Excalibur libs.
On the release side, there isn't that much left to do. I guess calling a
vote and go through the formalities should be enough to get the binaries
released to ibiblio.
Also, note that i primarily focussed on getting things to work and
compile. I did not do any work on cleaning up the transitive
dependencies of the poms.
At a first glance the dependencies don't look bad - everything which is optional
is set to "provided" (e.g. logkit, sourceresolve).
IMO it is very important to get an Avalon/Excalibur release, that will be pushed
to the central Maven repository, out of the door. I don't think it is a good
idea to do a non-milestone release which depends on the Apache snapshot repository.
Would it be possible to link Cocoon to your versions of Avalaon/Excalibur
artifacts in order to test them more widely?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
