AXIS Test Restructuring

[Matt Seibert <ms...@us.ibm.com>]

Prompted by a note from Steve Loughran this morning, and being budged by
some of my teammates, I am putting in that I am willing to chip in on the
restructuring.

Steve,

I have been working for about two weeks on the re-structuring of the test/
and samples/ compilation / execution process, being able to componentize
and instantiate any given test singularly, and making the system easier to
maintain and, hopefully, a little better organized.

I would like to speak with you about how I foresee the build/execution of
the test and samples structures changing in correlation to how you think
the overall build process should be changing.  I would very much like for
you to review my proposed changes, as well as see what your proposals are,
so as to produce the best possible output.

Please feel free to ping me back.  I am new to the axis community, and am
not quite sure how we all go about sharing information......

Matt Seibert                                           mseibert@us.ibm.com
IBM        External:    (512) 838-3656      Internal:   678-3656
----- Forwarded by Matt Seibert/Austin/IBM on 05/23/2002 14:42 -----



"Steve Loughran" <st...@iseran.com> on 05/22/2002 07:23:33 PM

Please respond to axis-dev@xml.apache.org

To:    "axis-dev" <ax...@xml.apache.org>
cc:

Subject:    [PATCH] ant build file still ugly




hmm, its been about a week since I pointed out that the main build.xml was
in trouble because

-it uses <property location> instead of <property value> , so paths work
property in sub-builds you run in their subdirectories

-it didnt have the descriptions that ant1.5beta1 requires when
calling -projecthelp

This patch is a repeat of the previous patches, with all changes
incorporated into the build file.

EVERYTHING STILL WORKS

This is not a complete rework of the build process, it is baby steps
towards
a robust build file tree. As such, the changes are minor; there is nothing
to fear.

Since my last posting was so completely ignored, I am going to open this as
a defect so you cant so easily neglect it. Also I will keep reminding you,
and if nobody has fixed it in a couple of weeks I am going to

a) assume that you are actually happy with the current state of the build
process, to the point that even baby steps are untenable
b) stop trying to fix it
c) update the ant documentation to cite xml-axis as how not to structure
large projects, probably in the Ant in Anger paper. Maybe I'll do this in
time for the next Ant1.5beta

Your choice :)

-steve

Re: AXIS Test Restructuring

[Steve Loughran <st...@iseran.com>]

----- Original Message -----
From: "Matt Seibert" <ms...@us.ibm.com>
To: <ax...@xml.apache.org>
Sent: Thursday, May 23, 2002 12:48 PM
Subject: AXIS Test Restructuring


> Prompted by a note from Steve Loughran this morning, and being budged by
> some of my teammates, I am putting in that I am willing to chip in on the
> restructuring.
>
> Steve,
>
> I have been working for about two weeks on the re-structuring of the test/
> and samples/ compilation / execution process, being able to componentize
> and instantiate any given test singularly, and making the system easier to
> maintain and, hopefully, a little better organized.
>
> I would like to speak with you about how I foresee the build/execution of
> the test and samples structures changing in correlation to how you think
> the overall build process should be changing.  I would very much like for
> you to review my proposed changes, as well as see what your proposals are,
> so as to produce the best possible output.
>
> Please feel free to ping me back.  I am new to the axis community, and am
> not quite sure how we all go about sharing information......

I am new to axis too, but worked on other apache projects. we can discuss
stuff on the dev mail list as it stores the discussion and lets other people
get involved; it "eliminates surprises"

So, write up your proposed changes and see where you think we should go.

Me, I think that as well as cleaning up the build process, we need to work
on the test suite so it runs more like a big fat junit test; you run all the
tests and get back an XML file of what worked, what didnt...to date the way
we go right now the first failure seems to stops the run.

I dont know quite how to do that (yet), though I have some definate ideas,
which revolve around how ant's unit tests run build files inside junit, but
with a bit more template driven generation of build files, and maybe even
the junit test cases to call them.

-steve