cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: pipelineComponent scope troubles (was Code freeze?)
Date Wed, 19 Sep 2007 11:28:15 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Felix Knecht wrote:
>> Is this failing test case a blocker for the release? In my opinion not
>> because everything else seems to work.
>>
>> WDOT?
>>
> I don't think it's a blocker:
> 1. We wouldn't be the only ones releasing (just in case it's a real bug
> and not a testcase problem) and having a release note with already known
> bugs.
> 2. It's a RC (2). Why are (just in case) already known bugs not allowed?
> 3. It would be really nice to see the RC2 released for the CocoonGT
> (Please go ahead with the release.)!
> 4. If ever I'd rather consider the 'pipelineComponent Scope troubles' as
> a problem than the zipper stuff.

Felix

As you have a similar environment as I have, could you give the sample from Grzegorz a try
with the
latest trunk (including changes from Grzegorz of today)?

First build (mvn clean install) myBlock2, than myBlock1, and afterwards myCocoonWebapp. Let
it run
and point to http://localhost:8888/myBlock2/screens/obtain-data to see whether you get an
Exception
or data.

TIA

- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.6 (GNU/Linux)

iD8DBQFG8QfPLNdJvZjjVZARAn+VAKCiQ8gViZlM8+oF7RiLHBZL3Do01gCeKKJE
N6To1VPPVtLYZWgowty4hdc=
=dSUj
-----END PGP SIGNATURE-----

Mime
View raw message