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
