Andrew Borley wrote:
[snip]
Hi Tom,

Coming from the C++ side of Tuscany, I know we'd certainly be
interested in those C++ SDO tests - please get involved!

Cheers
Andrew

On 10/11/06, T Gould <[EMAIL PROTECTED]> wrote:
Kelvin -

We at Rogue Wave have been developing an SDO product, HydraSDO, and have a seires of tests that might be easiliy modified so as to exercise your Java SDO product. We would be very interested in providing our tests as well as
helping create a test environment (unless this has already been done) to
futher test the SDO product.  Additionally, we also have C++ tests.


tom gould
-------------------------------


Tom,

That would be great! We could definitely add more SDO C++ tests and use any input, contribution and help putting together our test environment. We are about to cut a C++ M2 release candidate so we could try to run some of your tests against it.

On Linux we currently don't have much of a test framework in the C++ projects, we are basically running test programs that exercise the SDO APIs from a "make check". I am not sure about the details on Windows, the guys working on Windows can probably help describe that. But basically there's room for improvement :)

Please feel free to jump in! Patches can be contributed through JIRA. You just need to go to http://issues.apache.org/jira/browse/TUSCANY, register, then create new issues and attach patch files or zips for example. Ideas get discussed in emails on this list. Let us know if you need any help with the infrastructure, JIRA, SVN etc.

I guess we could try to build your tests in one of our sandboxes or a branch first, depending on what needs to be done to adapt them and build them in our environment. What do you think would need to be done?

Are you familiar with how we currently build on Linux and Windows? Do you have any questions on how to set up your Tuscany development/build environment that we can help you with?

--
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to