On 4/21/06 9:56 PM "Glen Daniels" <[EMAIL PROTECTED]> wrote:
> As we've discussed before, we should think about having various levels > of testing included in our available targets. This makes it feasible to > have interoperability testing included in our codebase, but not executed > when a user is offline, or making only small changes. > ... > Dev - just run unit tests, no serious integration tests. This should > essentially be a "sanity check" for quick development builds. Should > not include deep integration tests with complex extensions or big WSDLs. > This build should be kept, I'd like to hope, under 5 minutes on a > reasonable machine. > ... > Thoughts? Let me add something here: Just a few days ago I started to play around with axis2 sources. Maybe it's just my personal averseness to maven. But this is what I did: - svn checkout - run maven - it took ages, seriously (it's like 70 minutes on my PowerBook 1.5Ghz including Apache download timeouts) - went offline - run maven war, got a new dependency which wasn't downloaded - war create just failed. To sum up things: To get going with axis2 source is just disappointing. What do I need to do to ensure that all resources are available? How can I speed up rebuilding my sources? Where do I get sources for axiom/ws policy etc from? Also 5 minutes is just too long for someone looking into it for the first time. Whenever I create a build management system I tend to keep a rebuild after minor changes below 15-20 seconds. The lower, the better. (this is probably because I pay the people who sit there and wait for the build...) The first build can take longer, but the next one without clean should be just fast;) Jens
