Hi Eric,
I committed the changes - either ECM and YAAFI can be used as Avalon container of choice.
BTW, the Turbine build using CVS HEAD is broken and I'm not able to fix it
+) an unofficial Torque version was used and I had to replace it with the latest Torque 3.1.1 release in the project.xml
+) the build of the Torque extension fails on my box and enforcing the usage of an unreleased maven-torque-plugin makes me nervous since it could break my other builds.
Cheers,
Siegfried Goeschl
Eric Pugh wrote:
I'll echo Peter that if it is something that is optional versus mandatory, then that sounds great.. I assume your implementation looks somewhat like the existing container adapters?
Eric
On May 18, 2005, at 9:24 AM, Peter Courcoux wrote:
Hi Siegfried,
If this is done, which I believe is the case, as a service which can be enabled/disabled from TurbineResources.properties then I would say go ahead and commit to CVS HEAD.
Regards,
Peter
Siegfried Goeschl wrote:
Hi folks,
I integrated YAAFI into Turbine and the JUNIT test pass with YAAFI and ECM. Shall I commit the changes to CVS HEAD or work on a branch?!
I lean towards committing to CVS HEAD since I also need to delete the remaining Merlin artifacts from the CVS repo.
Cheers,
Siegfried Goeschl
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
