On 7/7/07, Grzegorz Kossakowski <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] pisze:
> Thank you. Lenya uses a ResourceExists Action. A Selector would be
> much more flexible. Now I have many XMAPs to revise.
No problem.
Just out of curiosity, does Lenya have plans about upgrading to Cocoon 2.2?
Since C2.2 is very near to final release, it's worthwhile for
Lenya community to consider such a move, IMHO.
--
Grzegorz Kossakowski
Lenya 1.4 is using Cocoon 2.1.x. Lenya 1.4 is long overdue; let it be
released with Cocoon 2.1.
Working against development versions of dependencies is insane. The
Lenya project has had problems because the devs keep upgrading to the
latest versions of dependencies. We cannot know if something broke
because of a commit to Lenya or an upgrade to a dependency.
I push to choose a certain release of each dependency when a new
version is started, then do not upgrade any dependencies unless a
specific feature in a dependency is necessary for the project. I have
a branch that I paused last year; I will upgrade the dependencies to
the latest gold versions when I return to the work (probably August or
September) and then not change any until after a release. That will
likely include Cocoon 2.1.10. Cocoon 2.2 is not even mentioned on the
Cocoon home page.
Java 1.6 has several standard features that will make Cocoon much
simpler (like the compiler API.) Cocoon releases twice each year.
Does the Cocoon project upgrade the dependencies while developing a
release? Is Java 1.6 even being considered? (I hope not because I
need Cocoon to run with Java 1.4 for two projects.)
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
