Ok ... so the first BlazeDS 4.7-SNAPSHOT is now available: https://repository.apache.org/content/repositories/snapshots/org/apache/flex/blazeds/
Unfortunately I had to deploy these snapshots from my local machine. In order to have the Jenkins automatically deploy the nightly build snapshots, we need to add a settings.xml to the build that contains the credentials for the deployment to the Apache servers. Unfortunately I doubt that anyone is willing to write his Apache Credentials in a plain text textfile ... I think for this we need to setup a dedicated technical user. But we probably need to order this from Infra. @Alex ... could you request this? As soon as you provide me with the credentials I'll whip up a settings.xml that should enable our Jenkins to deploy nightly builds. Chris -----Ursprüngliche Nachricht----- Von: Christofer Dutz [mailto:christofer.d...@c-ware.de] Gesendet: Montag, 5. Mai 2014 22:35 An: dev@flex.apache.org Betreff: AW: AW: Update to BlazeDS to make Testsuite pass It will be almost identical ... it's not missing anything that the Adobe version had, you are just able to provide a BlazeDS configuration from the applications Classpath (Was actually allways missing this feature and now I needed to implement this for the tests). So in any case changing the old jar with the new one will not make any difference. Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Montag, 5. Mai 2014 22:26 An: dev@flex.apache.org Betreff: Re: AW: Update to BlazeDS to make Testsuite pass Sounds good. Do you feel confident we have the right pieces and nothing is missing? IOW, will the flex-messaging-common.jar be the equivalent or better than the one we download from Adobe? Thanks, -Alex On 5/5/14 1:18 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >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
