Ok ... so I just committed a major update to BlazeDS ... now we should be able to publish SNAPSHOTS from Nightly builds and the Testsuite no longer needs a server up and running. I even had to implement a new Feature allowing to configure a BlazeDS server using a configuration located in the classpath and not on the file system (Needed that for the embedded jetty to be able to configure the test instance) I also updated the Ant scripts and it should be possible to build BlazeDS on a windows machine (Seems this has been an issue for quite some time judging from the Google results on this problem)
Now I think I'll concentrate on the SNAPSHOT deployment to Apache Central and as soon as that's done I'll finish the last bits of the still open issues. Chris -----Ursprüngliche Nachricht----- Von: Christofer Dutz [mailto:christofer.d...@c-ware.de] Gesendet: Sonntag, 4. Mai 2014 11:25 An: dev@flex.apache.org Betreff: AW: Update to BlazeDS to make Testsuite pass Actually I have excluded the testsuite artifacts from the deploy phase so they wouldn't be deployed when doing a release. In the maven world, running the tests during a release is good practice. Chris -----Ursprüngliche Nachricht----- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Sonntag, 4. Mai 2014 05:27 An: dev@flex.apache.org Betreff: Re: Update to BlazeDS to make Testsuite pass Hi, >> The old testsuite seemed to require a BlazeDS server running on the >> same machine The tests don't have to be part of a release, it would be of good know how to set an an environment to run then. >> What I did now was to add a "testsuite" module to the "modules" >> directory and moved all tests (actually only core had any) to that module. Sounds good to me. >> I didn't however want to commit this without asking you guys here. >> First I would like to hear if there are any objections to that change No objections from me. Thanks, Justin
