TextLayout was donated to Apache Flex so it won't be needing all that license hassle in the next release.
-Alex On 9/29/12 4:47 AM, "christofer.d...@c-ware.de" <christofer.d...@c-ware.de> wrote: > Ups ... > > Just saw that these seems to be a way ... the pom allows defining license > information: > http://maven.apache.org/pom.html#Licenses > I think I'm going to extend the generator to automatically add such a license > headers to the poms. So as soon as there is such a plugin, this could be used. > Eventually someone at Stackoverflow might even give me a pointer to existing > functionality that I didn't find yet. > > Unfortunatley I think adding these headers might be a pretty tricky task > having a look at how the licenses are currently being defined. > > In the root of the FDKs the license htmls contain some information about which > elements have which license, some the libs themselves sometimes have license > files accompaning them. > Some have License files inside the jars root ... some inside the jars META-INF > directory :-( ... guess it would be the best way to manually create a mapping > file telling the generator which version of which file has which license in > order to generate this pretty valuable additional information. > > I guess inside the framework things are a lot simpler ... assuming textLayout > and osmf being the only resources not having the Adobe Flex SDK License > Agreement (For Adobe FDKs) or Apache v2 (For Apache FDKs). > > 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: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] > Gesendet: Samstag, 29. September 2012 13:18 > An: flex-dev@incubator.apache.org > Betreff: AW: Flex Maven FDK Generator RC1 > > 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 > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
