Hi Alexis, thanks for changing the test port. I just changed the CI configuration to run the HTTP tests, too. Unfortunately there are several errors and the execution of the tests seem to stuck.
I don't really understand what's going wrong there :( Do you? Here is the transcript: http://hudson.zones.apache.org/hudson/job/ODE-trunk-jdk6/18/console Thanks, Tammo Alexis Midon wrote: > Hi guys, > > you may have seen the Jira updates but just in case: > > . The new HTTP port for tests in axis2-war is 8888. > https://issues.apache.org/jira/browse/ODE-384 > . axis2-war module now use TestNG as unit test framework > https://issues.apache.org/jira/browse/ODE-387 > > Alexis > > > On Thu, Oct 9, 2008 at 4:14 PM, Alexis Midon <[EMAIL PROTECTED]> wrote: > >> ok, working on it. >> >> https://issues.apache.org/jira/browse/ODE-384 >> >> Alexis >> >> >> >> On Thu, Oct 9, 2008 at 3:05 PM, Tammo van Lessen <[EMAIL PROTECTED]>wrote: >> >>> Alexis Midon wrote: >>>> Hi all, >>>> >>>> I really feel more and more constrained by JUnit these days. The only >>> fancy >>>> things we get are setUp and tearDown. thrilling... >>>> In the other corner of the ring is TestNG. TestNG comes with many nice >>>> things like various configuration hooks (BeforeSuite, BeforeClass, etc), >>>> data providers**, test factories and so on. JUnit 4 is only a pale copy >>> of >>>> what TestNG provides. >>>> >>>> So I'd like to know your opinion about migrating to TestNG. The >>> migration >>>> path is fairly easy. TestNG provides a JUnit converter. I've tried it on >>> a >>>> few modules. Of course there is no need to migrate all modules now. I'd >>> like >>>> to start with axis2-war. >>>> >>>> Waiting for your +1/-1. >>>> >>> +1 if this helps. >>> >>> While we're at it, do you think it's possible to make the HTTP port >>> configurable? Port 8080 seems to cause some troubles on our hudson build >>> server, that's why I have disabled it until there's a solution. >>> >>> Cheers, >>> Tammo >>> >> >
