On 4/30/14 7:40 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>> >> 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? >> > >+1, all Flex projects 'are' ant. Hopefully BlazeDS won't become an >exception... I don't have any objection to adding Maven builds to our CI server if someone wants to do it, but yes, it would be best to be able to make changes to the source for the one BlazeDS jar the SDK uses without requiring Maven. I think we do have the option of taking the source from BlazeDS like we do for TLF. Have the main SDK build do a BlazeDS jar build and package the required sources when building a release. -Alex
