Stephen McConnell wrote:
Sylvain Wallez wrote:Stephen McConnell wrote:
Let me give some details, since I'm currently working on sourceresolve after some discussion with Carsten. We want to reach API stability on this, because it's used in many places in Cocoon and a such is required if we want to start releasing Cocoon 2.1 (we're not even alpha yet).Agreed.To answer your questions, the plan is to start by refining and stabilizing the API and document it, and test into Cocoon 2.1. There's no problem if we start by testing with Cocoon before writing automated unit tests because of the unreleased nature of the 2.1 branch.Setting up a simple tesdt case should not be difficult.
Detailed docs and automated unit tests will be written in a second phase, and any help in this area is more than welcome !
I can help to put in place some very basic - but I'll need assistance when it comes down to using the package because I don't know anything about it (but I'm interested all the same).
OK. We'll talk about this after the first phase. I'm also interested in setting up those tests, as I never used the ExcaliburTestCase up to now and want to get up to speed with it, as it is _the_ key to write component test cases.
Also, I don't see a dependency of sourceresolve on pool. Where did you find it (I'm not fully "fluent" with Avalon build system) ?There were references to excalibur-pool-1.1 in the properties and build file. I checked the sources and you correct - the dependency isn't real. I've already updated and committed the respective files so your now only dependent on framework 4.1.3.
Cool. Thanks. Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
