Santiago Gala wrote:
Raphael Luta wrote:
Actually the issue is threefold:
- currently the Engine needs to initialize the Cocoon engine because
it uses its MemoryStore component for caching in memory portlets.
This implies that Cocoon *must* be correctly configured in order
-Original Message-
From: Raphael Luta [mailto:[EMAIL PROTECTED]]
Sent: Montag, 13. November 2000 00:19
To: JetSpeed
Subject: [vote] Miscellanous items
I'd like that all committers vote on the following points
in order to better define what needs to be done in the
clean-up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Luta [EMAIL PROTECTED] writes:
I'd like that all committers vote on the following points
in order to better define what needs to be done in the
clean-up/bugfix process for 1.2:
Point 1: Project module
In the CVS, in /modules/project
At 00:18 2000-11-13, you wrote:
I'd like that all committers vote on the following points
in order to better define what needs to be done in the
clean-up/bugfix process for 1.2:
Point 1: Project module
In the CVS, in /modules/project sits a project management
code contributed by Sandy Metzger
Raphael Luta wrote:
I'd like that all committers vote on the following points
in order to better define what needs to be done in the
clean-up/bugfix process for 1.2:
Point 1: Project module
In the CVS, in /modules/project sits a project management
code contributed by Sandy Metzger and
Santiago Gala wrote:
Raphael Luta wrote:
Point 2: Cocoon support
In my TODO list for 1.2, I mentioned that the Cocoon
support was a hack and was going to fail with Cocoon 1.8.
I proposed to remove completely its use from the engine
(thus affecting MemoryStore and a few basic
I'd like that all committers vote on the following points
in order to better define what needs to be done in the
clean-up/bugfix process for 1.2:
Point 1: Project module
In the CVS, in /modules/project sits a project management
code contributed by Sandy Metzger and apparently left alone.
This
