Hi Alex, But I think adding not adding potentially very usefull information, just because noone uses it will certainly not help the tag being used some day ;-) .. I know that Artifactory Pro for example allows to filter artifacs based on this information. So I think adding these tags to the pom will not do any harm, but provide some information that could be valuable in the future.
What groupId are you talking about? The general gid I was using "com.adobe.flex", "com.adobe.flash" and "com.adobe.air"? If Adobe would like to have something different here, now is the time for me to adjust this. So please simply tell me what to use instead ... I am also glad to change anything else Adobe or Apache would like me to change. This is the main reason for taking this issue to this mailinglist :-) In the end I would like to have Mavenized FDKs all participants can live with. Chris ________________________________________ Von: Alex Harui [aha...@adobe.com] Gesendet: Dienstag, 16. Oktober 2012 01:25 An: flex-dev@incubator.apache.org Betreff: Re: AW: Flex Maven FDK Generator RC1 Finally got time to read a little about this. Since there is currently no official usage of the license tag, I think I would rather try to prompt the user like we do now in the Ant build. It looks like this might be achievable via maven-antrun-plugin. I looked at the POMs in the link you sent. That seems pretty straightforward although Adobe might want a different groupId. But then we'd need to add the use of maven-antrun-plugin to these POMs in order to prompt for the Adobe license right? 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
