You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2014/04/30 09:42:32 UTC

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

AW: Has anyone been able to build BlazeDS?

Posted by Christofer Dutz <ch...@c-ware.de>.

Well it actually builds now ... just that it doesn't fail on test-errors ... 
All artifacts are create correctly.

Chris


________________________________________
Von: Erik de Bruin <er...@ixsoftware.nl>
Gesendet: Mittwoch, 30. April 2014 16:23
An: dev@flex.apache.org
Betreff: Re: Has anyone been able to build BlazeDS?

Chris,

Let me know when you have BlazeDS building consistently on Windows. I'll
then create a CI job for it on our new server.

EdB




On Wed, Apr 30, 2014 at 3:49 PM, Christofer Dutz
<ch...@c-ware.de>wrote:

> 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 <ch...@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 <ch...@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 <ch...@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
>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Has anyone been able to build BlazeDS?

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Chris,

Let me know when you have BlazeDS building consistently on Windows. I'll
then create a CI job for it on our new server.

EdB




On Wed, Apr 30, 2014 at 3:49 PM, Christofer Dutz
<ch...@c-ware.de>wrote:

> 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 <ch...@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 <ch...@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 <ch...@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
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

RE: AW: AW: Has anyone been able to build BlazeDS?

Posted by Frédéric THOMAS <we...@hotmail.com>.

I can't see blazeds in fisheye, did someone did the request for this repo to be plugged to already ?

Frédéric THOMAS

> From: webdoublefx@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: AW: AW: Has anyone been able to build BlazeDS?
> Date: Wed, 30 Apr 2014 15:05:43 +0100
> 
> > Oh cool ... so not only NSA is reading my posts :-) 
> 
> :-D
> 
> > Does anyone here know why the version in the project was 4.5.0.0 (I
>  incremented that to 4.6.0.0) but the latest released version is 
> something 4.0.1 ... what happened with all the stuff in between?
> 
> The last nightly build was on Tue May 24, 2011 [1] I can only guess they continued to work on it but didn't make it public.
> 
> Frédéric THOMAS
> 
> [1] http://sourceforge.net/adobe/blazeds/wiki/download%20blazeds%204/
> 
> > From: christofer.dutz@c-ware.de
> > To: dev@flex.apache.org
> > Subject: AW: AW: Has anyone been able to build BlazeDS?
> > Date: Wed, 30 Apr 2014 13:57:36 +0000
> > 
> > Oh cool ... so not only NSA is reading my posts :-) 
> > 
> > Does anyone here know why the version in the project was 4.5.0.0 (I incremented that to 4.6.0.0) but the latest released version is something 4.0.1 ... what happened with all the stuff in between?
> > 
> > Chris
> > 
> > ________________________________________
> > Von: Frédéric THOMAS <we...@hotmail.com>
> > Gesendet: Mittwoch, 30. April 2014 15:53
> > An: dev@flex.apache.org
> > Betreff: RE: AW: Has anyone been able to build BlazeDS?
> > 
> > > Ok ... I know I'm sort of having quite a monologue here, but I want this stuff logged ;-)I'm interested in what you're doing / discovering and I guess / hope I'm not the only one !
> > 
> > Frédéric THOMAS
> > 
> > > From: christofer.dutz@c-ware.de
> > > To: dev@flex.apache.org
> > > Subject: AW: Has anyone been able to build BlazeDS?
> > > Date: Wed, 30 Apr 2014 13:49:50 +0000
> > >
> > > 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 <ch...@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 <ch...@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 <ch...@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
>

RE: AW: AW: Has anyone been able to build BlazeDS?

Posted by Frédéric THOMAS <we...@hotmail.com>.

> Oh cool ... so not only NSA is reading my posts :-) 

:-D

> Does anyone here know why the version in the project was 4.5.0.0 (I
 incremented that to 4.6.0.0) but the latest released version is 
something 4.0.1 ... what happened with all the stuff in between?

The last nightly build was on Tue May 24, 2011 [1] I can only guess they continued to work on it but didn't make it public.

Frédéric THOMAS

[1] http://sourceforge.net/adobe/blazeds/wiki/download%20blazeds%204/

> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: AW: Has anyone been able to build BlazeDS?
> Date: Wed, 30 Apr 2014 13:57:36 +0000
> 
> Oh cool ... so not only NSA is reading my posts :-) 
> 
> Does anyone here know why the version in the project was 4.5.0.0 (I incremented that to 4.6.0.0) but the latest released version is something 4.0.1 ... what happened with all the stuff in between?
> 
> Chris
> 
> ________________________________________
> Von: Frédéric THOMAS <we...@hotmail.com>
> Gesendet: Mittwoch, 30. April 2014 15:53
> An: dev@flex.apache.org
> Betreff: RE: AW: Has anyone been able to build BlazeDS?
> 
> > Ok ... I know I'm sort of having quite a monologue here, but I want this stuff logged ;-)I'm interested in what you're doing / discovering and I guess / hope I'm not the only one !
> 
> Frédéric THOMAS
> 
> > From: christofer.dutz@c-ware.de
> > To: dev@flex.apache.org
> > Subject: AW: Has anyone been able to build BlazeDS?
> > Date: Wed, 30 Apr 2014 13:49:50 +0000
> >
> > 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 <ch...@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 <ch...@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 <ch...@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

AW: AW: Has anyone been able to build BlazeDS?

Posted by Christofer Dutz <ch...@c-ware.de>.

Oh cool ... so not only NSA is reading my posts :-) 

Does anyone here know why the version in the project was 4.5.0.0 (I incremented that to 4.6.0.0) but the latest released version is something 4.0.1 ... what happened with all the stuff in between?

Chris

________________________________________
Von: Frédéric THOMAS <we...@hotmail.com>
Gesendet: Mittwoch, 30. April 2014 15:53
An: dev@flex.apache.org
Betreff: RE: AW: Has anyone been able to build BlazeDS?

> Ok ... I know I'm sort of having quite a monologue here, but I want this stuff logged ;-)I'm interested in what you're doing / discovering and I guess / hope I'm not the only one !

Frédéric THOMAS

> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: Has anyone been able to build BlazeDS?
> Date: Wed, 30 Apr 2014 13:49:50 +0000
>
> 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 <ch...@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 <ch...@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 <ch...@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

RE: AW: Has anyone been able to build BlazeDS?

Posted by Frédéric THOMAS <we...@hotmail.com>.

> Ok ... I know I'm sort of having quite a monologue here, but I want this stuff logged ;-)I'm interested in what you're doing / discovering and I guess / hope I'm not the only one !

Frédéric THOMAS

> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: Has anyone been able to build BlazeDS?
> Date: Wed, 30 Apr 2014 13:49:50 +0000
> 
> 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 <ch...@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 <ch...@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 <ch...@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

AW: Has anyone been able to build BlazeDS?

Posted by Christofer Dutz <ch...@c-ware.de>.

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 <ch...@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 <ch...@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 <ch...@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

AW: Has anyone been able to build BlazeDS?

Posted by Christofer Dutz <ch...@c-ware.de>.

Ok ... done :-)

Now a simple "mvn install" in the "modules" directory (not the root of the project) should build BlazeDS successfully.

Chris

________________________________________
Von: Christofer Dutz <ch...@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,

Chris

________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Mittwoch, 30. April 2014 09:42
An: dev@flex.apache.org
Betreff: Has anyone been able to build BlazeDS?

Hi,

Chris

AW: Has anyone been able to build BlazeDS?

Posted by Christofer Dutz <ch...@c-ware.de>.

Hi Guys,

Chris

________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Mittwoch, 30. April 2014 09:42
An: dev@flex.apache.org
Betreff: Has anyone been able to build BlazeDS?

Hi,

Chris