Hi Alex,

well unfortunately it doesn't deal with licenses, so you can't sort of have the 
license type as metadata and tell your build that you only want Apache License 
Stuff in your build. Would be a great feature though ... think I might relay 
this question to the Maven list ;-)

Chris




[ C h r i s t o f e r  D u t z ]

C-Ware IT-Service
Inhaber
Dipl. Inf. Christofer Dutz
Karlstraße. 104, 64285 Darmstadt


   IT- und Systemhäuser

fon:  0 61 51 / 27315 - 61
fax:  0 61 51 / 27315 - 64
mobil:  0171 / 7 444 2 33
email:  christofer.d...@c-ware.de
http://www.c-ware.de

UStId-Nr. DE195700962

-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aha...@adobe.com] 
Gesendet: Donnerstag, 27. September 2012 00:11
An: flex-dev@incubator.apache.org
Betreff: Re: Flex Maven FDK Generator RC1

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

Reply via email to