Hey there, But if Maven is used for dependency management then we don't need to include any third party stuff in our repositories. You just reference the appropriate remote repositories and the build system will pull in the necessary files. That's the nice option of using GradleFX, it uses the convenience of the Maven dependency system combined with a sane build syntax. Or am I missing a point somewhere?
cheers, Roland On 13 February 2012 16:21, Martin Heidegger <m...@leichtgewicht.at> wrote: > > On 14/02/2012 00:14, Alex Harui wrote: > >> My understanding is we should not check in swcs >> >> Sent from my Motorola ATRIX™ 4G on AT&T >> > Quote from Apache licensing [1]: > > By including only the object/binary form, there is less exposed surface > area of the third-party > work from which a work might be derived; this addresses the second > guiding principle of this > policy. By attaching a prominent label to the distribution and requiring > an explicit action by the > user to get the reciprocally-licensed source, users are less likely to be > unaware of restrictions > significantly different from those of the Apache License; this addresses > the fourth guiding > principle of this policy. > > That does look a lot like we can include 3rd party libraries if their > licenses match. Like any other, > ordinary, As3 project. Flex could also use dependencies. Would that be so > much horror? > > I understand that its not favorable but in contrary to core code: These > 3rd party librarys would > only be included to run the framework but to run the tests. > > yours > Martin. > > [1] > http://www.apache.org/legal/**3party.html#category-b<http://www.apache.org/legal/3party.html#category-b> > -- regards, Roland -- Roland Zwaga Senior Consultant | Stack & Heap BVBA +32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com
