Wow, now we're all confused. Let me try to summarise: 1) we can't have the as3commons/zip SWC as part of the project, as it is a binary. 2) we can however checkout the as3commons/zip AS files and put those in the project, since they have compatible licenses (right?) . This is what we did with MD5Stream from as3corelib. 3) since the source will be part of the project, there is no need to go to Maven or whatever from the build script. If the project compiles, the build script will run fine. 4) ... 5) profit
;-) EdB On Thu, Aug 16, 2012 at 10:53 AM, Roland Zwaga <rol...@stackandheap.com> wrote: >>> > I'm sorry, my daily dose of caffeine clearly hasn't kicked in yet. How >>> > would this work? If the swc is not part of the Flash builder project, >>> > how would we be able to use it? How is this better than including the >>> > actual source files, like we do for the crypto components? >>> >>> Maybe I misunderstood Bertrand's message wrong. If it is allowed to >>> directly check out the code and make a build from that, then by all means, >>> go for that ;) >>> >>> Roland >>> >> >> Now I am confused. To be clear, we would have to copy the code from >> as3commons and put it in the flex svn repo. And we release the as3commons >> source as part of the installapacheflex source release (of course with all >> the attributions) > > Hey Om, > > from what I understood the prcoess would be that the build script > would just check out > the as3commons source, and use that source, together with the Flex > installApacheFlex > source to create a binary. > But, like you mention, I also think that just downloading the binary > dependencies would > probably be easier. > > Roland -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
