Hi everyone, David Illsley has set up a Continuum Server for Axis2 [1] and I asked him to include Woden too. The Woden build isn't feeding into the Axis2 build (yet). Continuum is using our buildAll Ant target but since junit.jar isn't on the classpath the tests aren't running (see David's post to axis-dev [2]). Every hour Continuum will run svn update on its working copy of the Woden trunk and if there are changes, will start a build. It the report for each build it will include a table of the commit log since the previous build.
The benefit of having a continuous integration server is that Axis2 can spot very quickly when we change an interface (which we will do with WODEN-120 when we change the return type of readWSDL()). Likewise we can track our dependencies more closely (e.g. we depend on Axiom 1.1.1 right now but we could move up to v1.2.2). Where next? ... These are things we could do in the Continuum build * have Continuum email woden-dev a report for each build (or perhaps just when it fails) * run the unittests (will need to re-jig the tasks so only junits that currently pass are included) * run the interop tests (will need a task in the main build.xml to execute the ant-test/build.xml) * move to using maven pom to ensure we pick up the latest levels of our dependencies (and eventually bring the maven pom up to the functionality we have in our Ant scripts btw: I believe maven can execute Ant so we don't need to convert the interop build.xml to maven if we don't want to) Any comments? [1] http://ws.zones.apache.org:10000/continuum/servlet/continuum/target/Summary.vm/fid/continuumProject [2] http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200701.mbox/[EMAIL PROTECTED] BTW: thanks David for setting this up. Cheers, Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
