Either way, if they have been available, unrestricted, for a prolonged period, without Adobe actively contesting the right of Velo - or anyone else - to distribute them, then they are de facto in the public domain.
EdB On Fri, Sep 19, 2014 at 6:21 PM, Alex Harui <aha...@adobe.com> wrote: > Which jars are you talking about? Are you sure they are in Maven Central? > > The issue is that back in the day, Flex management was more interested in > growing the market for Flex than in making sure all of the licensing and > trademark rules were being followed. They may or may not have given Velo > permission, and if they did, may not have checked with Adobe Legal first, > and if they didn't give permission, may not have cared that Velo posted > them. > > -Alex > > On 9/19/14 12:32 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > > >Hi, > > > > > >today I'll be working hard on integrating the Mavenizer into Flexmojos. > >While this will resolve the hard dependency on Air and Flash libraries > >making it possible for us to release Apache Flex in Maven, there still > >are some dependencies to third party libs. For example the Font handling > >stuff ... > > > > > >Now I just had the idea that Velo did have an official permit to release > >earlier versions of Adobe Flex and with this I bet some libs were > >released that we still need to manually download. I doubt these have > >changed in the last years. So how about referencing these libs that are > >already in Maven Central? Cause I think without this we wouldn't be able > >to officially release Flex as Maven? > > > > > >Chris > > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
