Given
my limited ant skills, this looks like a good start.
I
would prefer that the component build files are named 'build.xml' so I can go to
a component directory and invoke 'ant' without the -buildfile argument. It
seems as if I cannot build/deploy/test without invoking ant from the top
level. I would prefer to do this from the component directory (i.e. 'cd
samples/echo; ant compile' or 'cd test/wsdl/import; ant
test' ).
I do
like the top level buildTest and buildSample filenames however, and would expect
their default targets to build/test everything.
I
would like to see details on the process of adding a new test in the unit,
functional and WSDL areas.
--
Tom
Jordahl
Macromedia
-----Original Message-----All:
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 10, 2002 5:30 PM
To: [EMAIL PROTECTED]
Subject: Proposal for Test and Samples Changes
Attached is an HTML document with a little more description of my proposed changes to the way that Tests and Samples are handled in AXIS. Please note, most of this is what I have already done, and functioning with no regressions to function.
Please give me any feedback you feel appropriate, especially telling me where I need more detail / more description. I will try to get a "sample implementation" document together over the next few days so that you can better visualize the process flow.
(See attached file: AxisTestRedesign.html)
Matt Seibert [EMAIL PROTECTED]
IBM External: (512) 838-3656 Internal: 678-3656
