Stephan Nagy wrote:
>The testbed stuff now compiles just fine, the 'fix' involved removing the
>imports for openxml, thats it delete 4 lines of code. TestBed.java is just
>that 'our' testbed it isn't gauranteed to compile or work at any given
>moment, thus the name testbed. It does however contain useful examples if
>you want to look at the source, and take the time to understand what they
>do. Like jon said this isn't rocket science.
Thank you for your work. I do expect to find ecs very valuable, and hope to
contribute ASAP. Coming from a world of Extreme Programming, I had come to
expect regression tests to be constantly working and to detect errors
automatically, and mistakenly assumed that TestBed.java was such a test.
Once I understand this stuff, I will probably volunteer to create such a
test based on JUnit if the active developers would like to adopt that
practice. I have found it to be one of the fastest ways to learn new code,
as the test tells you what it expects to find and how it expects to make it
happen.
>Me and Jon both do this in our 'spare' time, and quite honestly only a
>handful of the users of ecs have contributed anything back to the project.
>I ( like most other developers I know ) despise creating documentation, and
>am not apt to do anything that i despise in my 'spare' time. If someone
>out there wants to pay me to create documentation for ecs I might do it.
>If someone out there wants to contribute and create a more useful set of
>documentation we would be happy to add it to the project.
Well, I'm with you on hating to do documentation. If I do find myself
creating some for my co-workers I will happily contribute it.
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
