Thorsten Scherler schrieb:
On Thu, 2008-01-03 at 23:45 +0100, Andreas Hartmann wrote:
Andreas Hartmann schrieb:
Andreas Hartmann schrieb:
Jörn Nettingsmeier schrieb:
Andreas Hartmann wrote:
Thorsten Scherler schrieb:
No, we will stick to our decision and release with cocoon head.
Since Cocoon 2.1.11 has been tagged, shall we set the svn:externals in
RELEASE_2_0 to this tag, or shall we keep it at BRANCH_2_1_X?
RELEASE. it might be necessary to roll lenya-2.0a tarballs if
significant changes crop up during the cocoon release, but i doubt it's
going to happen.
It looks as if there have been some changes to the build process. The
Xalan jar is not copied to WEB-INF/lib anymore, which makes the tests
fail and prevents Lenya from starting up. I'll try to find out what
goes wrong.
The endorsed libs are now only in WEB-INF/lib/endorsed. Apart from that,
externals/cocoon_2_1_x is hard-coded in lenya.sh. Can we change this to
the following declaration?
ENDORSED_LIBS="${LENYA_WEBAPP_HOME}/WEB-INF/lib/endorsed"
It might be a bit risky to tweak our tagged version to work with Cocoon
2.1.11. I see two options:
a) Release the already tagged version with a Cocoon revision before the
critical changes
b) Update Lenya to work with Cocoon 2.1.11 and do another RC
I would prefer b) since it would be so much nicer to release 2.0 with a
stable cocoon 2.1.11.
Unfortunately the combination doesn't work at the moment, and I can't
estimate how long it will take to update Lenya and how risky this is.
Therefore I'm slightly in favor of a). I have specified the Cocoon
revision number in the RELEASE_2_0 tag, but if we decide to postpone the
release, we can still change it.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
