On Jan 3, 2008 6:16 AM, David Crossley [EMAIL PROTECTED] wrote:
...I used the tar.gz and verified the md5sum and pgp signature,
and investigated some other things.
md5: f103d7c90fcd1e0f027f88f7fd0a44a0...
Automated tests (both junit-tests and htmlunit-tests) work for me
on macosx / JDK 1.5,
Carsten Ziegeler pisze:
As this is currently the quiet season of the year, I'll leave the vote
open until monday.
Could you leave it open until today's night? I'll definitely want to have a
look at it.
--
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
Carsten Ziegeler wrote:
Hi,
i've put up the 2.1.11 release at:
http://people.apache.org/~cziegeler/releases/cocoon/
I'm just looking through JIRA and note that the version still uses an
antiquated version of ehcache. By that I mean, a version that does not
do large distributed caching
Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
As this is currently the quiet season of the year, I'll leave the vote
open until monday.
Could you leave it open until today's night? I'll definitely want to have a
look at it.
No problem, I'll close the vote tomorrow.
Carsten
--
Sorry for the noise, I'm having problems sending messages to Apache
mailing lists.
Ugo
Hi Alec,
This is a great improvement! However, we cannot use a newer ehcache
version, cuz we must keep cocoon 2.1.x branch compatible with java 1.3. :S
Currently, we use ehcache 1.2.3. The 1.2.4 did drop support for java 1.3 [1]
Best Regards,
Antonio Gallardo.
[1]
I was not able to test it with the CMS today, but on both my Ubuntu
laptop with JDK 1.5 and on my desktop WinXP JDK 1.4 all seems fine!
+1
Jeroen
On Mon, 2008-01-07 at 09:27 -0600, Antonio Gallardo wrote:
Hi Alec,
This is a great improvement! However, we cannot use a newer ehcache
I found the problem. The connection between Forrest and Daisy
on the ASF Zones server is very slow. The Cocoon-2.1 docs job
takes so long to complete, that it gets clobbered by another
cron job.
It seems to be a network issue that Forrest developers should
report to ASF Infrastructure. First we
David Crossley wrote:
Would someone please look at why a recent change in Daisy
seemed to break the automated building of 2.1 docs.
I am away now for our weekend.
http://article.gmane.org/gmane.text.xml.cocoon.devel/76511
Perhaps browse the docs@ list in the period prior to the
first
Ralph Goers wrote:
I didn't know about the plugin, but yes I knew I should have put the
issue number in the commit. I just forgot to do it.
Do:
svn propedit svn:log --revprop -r609282
https://svn.apache.org/repos/asf/cocoon/trunk
-David
Joerg Heinicke wrote:
On 06.01.2008 04:35, [EMAIL
Argh, forgot to Cc forrest dev.
-David
David Crossley wrote:
I found the problem. The connection between Forrest and Daisy
on the ASF Zones server is very slow. The Cocoon-2.1 docs job
takes so long to complete, that it gets clobbered by another
cron job.
It seems to be a network issue
On Jan 7, 2008, at 2:32 AM, Ralph Goers wrote:
But if they want to build the sample site and run it what would they
do?
Create pom.xml inheriting from core/cocoon-webapp and add dependencies
to all of the *-sample blocks you want, followed by mvn install
jetty:run should do it.
Vadim
How hard would it be to create an archetype to create the pom
automatically? Users would then either just build and run it or edit it
first to remove stuff they don't care about.
Telling them to create pom.xml inheriting from core-cocoon-webapp still
requires that they a) know how to do that
13 matches
Mail list logo
