On 8/16/12 5 :22AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>The crypto code I got from the as3corelib (Mike Chambers) at: > >https://github.com/mikechambers/as3corelib/blob/master/src/com/adobe/ > >The license at the top (included below) seems to indicate we can use >the source as long as the license is included. > >Please tell me if I was wrong to include the source in the project and >how to set things right. > >EdB > ><license> >/* > Copyright (c) 2008, Adobe Systems Incorporated > All rights reserved. > > Redistribution and use in source and binary forms, with or without > modification, are permitted provided that the following conditions are > met: > > * Redistributions of source code must retain the above copyright notice, > this list of conditions and the following disclaimer. > > * Redistributions in binary form must reproduce the above copyright > notice, this list of conditions and the following disclaimer in the > documentation and/or other materials provided with the distribution. > > * Neither the name of Adobe Systems Incorporated nor the names of its > contributors may be used to endorse or promote products derived from > this software without specific prior written permission. > > THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS > IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED >TO, > THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR > PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR > CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, > EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, > PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR > PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF > LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING > NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS > SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. >*/ ></license> > If you look that license is no longer at the top. I moved the copyright to LICENSE and put the Apache header on the top of the file. I added an entry to the NOTICE file. This code has a BSD license which is compatible with Apache so we can include the code without an issues as long as we handle the copyrights and notice correctly. As far as the as3commons source code goes we can do the same thing and include the code in our common directory and build the swc ourselves. Alternatively we can download the swc as part of the build process as we do currently for some of the other swcs. I can work on this later today or tomorrow. Carol > > >On Thu, Aug 16, 2012 at 10:33 AM, Om <bigosma...@gmail.com> wrote: >> On Thu, Aug 16, 2012 at 1:27 AM, Erik de Bruin <e...@ixsoftware.nl> >>wrote: >> >>> >> Then Flex can probably just use those modules as dependencies? >>> > >>> > Yup, I believe that would be the easiest, the build script for the >>> > installApacheFlex >>> > application will just need to download the swc from the Maven repo. >>> >>> 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? >>> >>> EdB >>> >>> >> Just like how anyone who wants to develop with Apache Flex source would >>do >> today. Download the sources, then run a script that would download all >>the >> dependencies. Then, set up your project and code away. Just don't >>check >> in the dependencies (if you are a committer) >> >> I think we need to talk about the Crypto components as well :-) Can you >> provide some details about where the source code is from and what >>license >> it is? If it is an incompatible license, we need to add that as a >> downloadable external dependency as well. >> >> Thanks, >> Om > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
