I had a longer reply to this, but outlook express crashed. (NB, everyone on XP: dont download the latest IE6 SP on windows update, it breaks their own apps)
> > I understand that Maven is considered dangerous. So, now that I am becoming > familiar with more of the Axis project I would think it should be considered > after Maven hits 1.0 which should be approximately the same time that Axis hits 1.2. As Sam said, we will happily add a maven build for you to the main files; this was the kind of evangelism that got ant to where it was. > > > One thing to look at in the Axis1.2 timeframe is the test system. > > > > I have an uncommitted rework of test.xml that used better patterns to > > provide an online/offline switch, but leakages in ant1.5.1 and sun.javac > > kept it out. Even though ant1.6 fixes the leak in <exec>, I still cant > > commit it, and now I am thinking of a better approach: glens. > > > > We all need to sit down and design a better test framework, one with > > -cached WSDL of various endpoints > > -template based (velocity?) generation of test messages and response > > verification > > -functional tests on tomcat, jetty, jboss > > -functional tests against .net & other soap implementations, testing > > stuff beyond what the soapbuilders test. > > > > > > I dont think rewriting the test/**/build.xml to maven-land is the right > > solution here. We need to be more revolutionary in test thinking -but > > still run on ant1.5 for the sake of everyone. > > After playing with the tests I would tend to agree. These things would be > great. However, it will be a week or so of playing/testing before I have more > thoughts on this. I was thinking about this over the weekend. I'll write up some thoughts in .dbk format and stick it up on CVS, and we can start thinking how to do it right.
