Ok ... I know I'm sort of having quite a monologue here, but I want this stuff logged ;-)
Just did another comit fixing most of the testsuite issues and fixing a I18N problem. I couldn't quite fix all issues as some of the tests require a BlazeDS server running on localhost:8400, which doesn't seem to be started by the testsuite and is expected to run. But what puzzled me even more, was that some tests, such as testConnect, testReconnect etc. were green. Having a look at the code I could see that a connection is really only opened as soon as someting is done. So a testConnect doesn't actually test if the client is able to connect. So I guess it makes sense to update the testsuite to acutally start a BlazeDS server as part of the testsuite and a lot of tests need some tweaking as a connection test, that doesn't actually test if a connection can be established is pretty worthless and I guess 75% of the connection related tests pass without a server being available. Chris ________________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Mittwoch, 30. April 2014 12:00 An: dev@flex.apache.org Betreff: AW: Has anyone been able to build BlazeDS? Ok ... done :-) so I just comitted some changes that allow us to build BlazeDS. Some tests are failling though, but it seems they were already failling with the BlazeDS team as they configured Maven not to fail on test errors. - Updated the repository urls to publich to Apache repos - Updated the groupId to org.apache.flex.blazeds - Updated the version to 4.6.0.0-SNAPSHOT - Fixed some minor issues that prevented the build to run Now a simple "mvn install" in the "modules" directory (not the root of the project) should build BlazeDS successfully. 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) Chris ________________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Mittwoch, 30. April 2014 11:09 An: dev@flex.apache.org Betreff: AW: Has anyone been able to build BlazeDS? Hi Guys, ok so I think I found the problem: It seems that the BlazeDS team was fedup with the Ant build and gave up on this (Actually it is impossible that it was able to run at all in its current state). To me it looks as if they switched to Maven a while ago (When having a look at the directory development\IDEA\projects all these projects are Maven projects). Unfortunately the build config saved here semms to be a little out of date as I wasn't able to build with these project settings. So I created a new project configuration but this time with maven. As soon as I selected modules/pom.xml as root of the project all things started working magically. I did have to tweak one or two things (The team must have manually added activemq libs and set the source directories in the IDE), but now I'm able to build blazeds using Maven :-) There are some tests failling though, which I will have a look at. If this is however correct, there are some things that should be addressed in the near future: - Currently the project is only buildable using maven, but the project structure is an Ant project where a lot of stuff had to be tweaked --> I would suggest to make the project use the default maven structure. From my experiance it's really bad to have a Maven project use an Ant directory layout as quite some Maven plugins tend to trip and fall on this. - I would suggest to remove the ANT scripts and everything related to the Ant build as they are completely throwing new users onto the wrong track Chris ________________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Mittwoch, 30. April 2014 09:42 An: dev@flex.apache.org Betreff: Has anyone been able to build BlazeDS? Hi, I have tried for the second evening to get BlazeDS to build. On my windows machine at first I am getting tons of missing lib directory errors. I seem to have resolved most of these by making the filesets not fire errors on missing resources. Unfortunately there are some classes with commented out imports that don't seem to have an implementation available (xalanImpl or whatever artifact they were in). I'll try to continue on this. Just wanted to know If anyone here was actually able to build BlazeDS yet. Chris
