Hi Alex, I understand that if your project download some required artifact from some official repo, that artifact should be there based in some license. If Adobe put some artifact in an official maven repo is because agree with whatever license it could have, so people could point to that artifact.
Other case will be a private maven repository that could have inside an artifact that break some license, but that case should not be important... 2012/9/27 Alex Harui <aha...@adobe.com>: > One more question (since we've been beating up the installer folks about > this): how does Maven deal with licenses? Our Ant script stops and requires > that you hit a key to accept a license. Can Maven do the same? Otherwise > it seems like you could end up downloading some dependency with a license > you didn't agree with. > > -Ale > > > On 9/26/12 2:59 PM, "Carlos Rovira" <carlos.rov...@codeoscopic.com> wrote: > >> That would be awesome! :) >> >> El miércoles, 26 de septiembre de 2012, christofer.d...@c-ware.de escribió: >> >> >>> Well in general it would be enough if Adobe simply published the >>> airglobal, playerglobal and osmf swcs along with their language resources >>> to a public repo ... only these 3 artifacts would be enough to make us all >>> really really happy and Apache could start officially deploying Flex FDKs >>> using maven without any legal issues. >>> >>> > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 CODEOSCOPIC S.A. Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
