Oh ... so I'll update that to 4.7 in the poms then. The problem with BlazeDS was that you actually never found the page where to download stuff from. I never got past 4.0.1, cause I never found the Download for anything more recent :-(
Think in that case I'll have to completely get to know BlazeDS again, because I bet a lot has happened since 4.0.1 :-( I'm currently working on the failing tests. So far I have managed to extend the tests that they startup an embedded Jetty with the MessageBrokerServlet on a given port ... so hopefully I'll be able to finish this this weekend. Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Donnerstag, 1. Mai 2014 07:08 An: dev@flex.apache.org Betreff: Re: AW: AW: Has anyone been able to build BlazeDS? BTW, the Adobe BlazeDS team says the latest public version is 4.6, not 4.5 or 4.0.1. -Alex On 4/30/14 9:34 PM, "Alex Harui" <aha...@adobe.com> wrote: >I took a look at the BlazeDS ant script. I fixed a few things and it >completed. The main target does not run any tests and I did not take >the time to try to run tests. > >-Alex > >On 4/30/14 8:12 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > >>Well the problem is, is that the Ant build is completely fu***d up ... >>it doesn't work at all. >>And it's no problem at all to call a maven build from Ant and vice-versa. >> >>Chris >>________________________________________ >>Von: Alex Harui <aha...@adobe.com> >>Gesendet: Mittwoch, 30. April 2014 16:38 >>An: dev@flex.apache.org >>Betreff: Re: AW: Has anyone been able to build BlazeDS? >> >>On 4/30/14 3:00 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >> >>>Now a simple "mvn install" in the "modules" directory (not the root >>>of the project) should build BlazeDS successfully. >>Excellent progress. Thanks for working on it. >> >> >>> >>>Next steps would be: >>>- to check the Errors in the Unit tests. >>>- to setup a Jenkins build to build and deploy snapshots (A simple >>>"mvn clean deploy" should do, after the credentials for deploying >>>have been >>>setup) >>>- Clean up the project (Remove old stuff and all Ant releated >>>scripts) >> >>Are you sure we don't need to keep the Ant scripts? BlazeDS is going >>to be upstream of the Flex SDK. >>It might be nice if the rest of the SDK committers can debug BlazeDS >>issues without having to set up Maven? >> >>-Alex >> >
