Well I think this would not be correct as OSMF is currently not in version 4.9.xxx, but 2.0 http://sourceforge.net/projects/osmf.adobe/files/ So in my opinion the version number in the Apache FDK is not correct. If the OSMF would one day reach 4.9 version numbers things would start getting really ugly cause then there would be repos containing 4.9 versions that are ages old as well as repos containing the new version. So I would strongly suggest only to set the versions of stuff that belongs to us.
Chris -----Ursprüngliche Nachricht----- Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Gesendet: Donnerstag, 31. Januar 2013 15:27 An: dev@flex.apache.org Betreff: Re: Splitting up Flex and Air? To be more precise, I would like to let the code as it is for the Adobe SDKs and assign the SDK version to the rsls for the Apache SDKs, would it be a problem ? -Fred -----Message d'origine----- From: Frédéric THOMAS Sent: Thursday, January 31, 2013 3:14 PM To: dev@flex.apache.org Subject: Re: AW: AW: AW: Splitting up Flex and Air? Hi Chris, I was happy trying that but it doesn't work, the current implementation which process rsls, getting the version number of the artifact extracting it from the original rls file is based on the assumption that Textlayout and OMSF can have a different version number than the SDK and make it a generality for all the rsls, which doesn't fit for my attemp. Even if this assumption is true for the SDK < 4.8, it's apparently not true for SDK >= 4.8, could we hardcode this as an exception for these 2 libs and assign the SDK version number for the others ? -Fred -----Message d'origine----- From: christofer.d...@c-ware.de Sent: Thursday, January 31, 2013 11:42 AM To: dev@flex.apache.org Subject: AW: AW: AW: Splitting up Flex and Air? Sure I'm fine with that :-) -----Ursprüngliche Nachricht----- Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Gesendet: Donnerstag, 31. Januar 2013 11:03 An: dev@flex.apache.org Betreff: Re: AW: AW: Splitting up Flex and Air? Ok, I don't need to change the AIR version, should work then, anyway, maybe add a step-by-step help in the readme for the last part as I didn't get everything :) Still, do you mind if in the SDKGenerator, I replace : // In general the version consists of the content of the version element with an appended build-number. String sdkVersion = version + "." + build; by: // In general the version consists of the content of the version element with an appended build-number. String sdkVersion = (build.equals("0")) ? version + "-SNAPSHOT" : version + "." + build; The build number will be set to 0 only if I do a temporary release from the sources, never in official releases. -Fred -----Message d'origine----- From: christofer.d...@c-ware.de Sent: Thursday, January 31, 2013 10:36 AM To: dev@flex.apache.org Subject: AW: AW: Splitting up Flex and Air? Hi Frederic, well as far as I know, as long as you use the Air version that was naturally bundled with the corresponding FDK, then all should work already. The only problem is that if you want to use a different Air SDK. Currently the adt of the original FDK is used, but it should be the version shipped with the desired Air SDK version. That's what I'm intending on doing. The only change you should need to use that updated version with FM would be that you need to add a "compiler" artifact for the Flex-SDK as well as one additional Air-SDK compiler artifact. Chris -----Ursprüngliche Nachricht----- Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Gesendet: Donnerstag, 31. Januar 2013 10:28 An: dev@flex.apache.org Betreff: Re: AW: Splitting up Flex and Air? Hi Chris, I'm doing an AIR App, so let me know when you update FM pls, like that I can test it, btw, do you mind if I update the mavenizer as when the Flex build number is 0, instead of having a version number + '.0', I put version number + "-SNAPSHOT" ? -Fred -----Message d'origine----- From: christofer.d...@c-ware.de Sent: Thursday, January 31, 2013 8:44 AM To: dev@flex.apache.org Subject: AW: Splitting up Flex and Air? Hi Om, Well I think this would definitely be a cool thing. Then the user will have several ways of getting a mavenized FDK (Intaller, Manually Mavenizing, Mavenizer integrated into the maven-flex-plugin and by using the auto-download-feature of the maven-flex-plugin (the one I was talking to Alex about)). But before officially adding this, I'd like to modify the mavenizer to correctly mavenize the Air compiler artifacts (adt.jar, smaili.jar and baksmali.jar) Chris -----Ursprüngliche Nachricht----- Von: omup...@gmail.com [mailto:omup...@gmail.com] Im Auftrag von Om Gesendet: Donnerstag, 31. Januar 2013 02:35 An: dev@flex.apache.org Betreff: Re: Splitting up Flex and Air? Chris, I meant to reply earlier, but forgot. The installer already downloads everything while displaying the required licenses along the way. Do you think having a "Mavenize" button at the end would be a good idea? We could just call your mavenize ant script from the AIR app. Please let me know if this is something you would be interested. I would be glad to help you out with this. Thanks, Om On Mon, Jan 28, 2013 at 9:20 AM, christofer.d...@c-ware.de < christofer.d...@c-ware.de> wrote: > Hey ... I was never talking about distributing them ... The mavenizer > is all about you downloading (after Accepting whatever license Adobe > wants you to accept). And then simply to transform this download on > your local machine. So every user that wants to use it has to mavenize > a FDK before using it. > > The tool I promised to create (as soon as I have the time to do so) > will take care of the downloading but at this point the Mavenizer > expects you to download the stuff manually and this code will be the > base for the tool I am intending on building ... but I don't want to > go into a discussion about this again. > > Currently I'll simply stick to mavenizing every jar in the Air SDK > into the groupId "com.adobe.air.compiler" and hard-code an exception > to omit the > 3 files from "com.adobe.flex.compiler" or "org.apache.flex.compiler". > I think this should do the trick. > > Chris > > -----Ursprüngliche Nachricht----- > Von: Alex Harui [mailto:aha...@adobe.com] > Gesendet: Montag, 28. Januar 2013 18:02 > An: dev@flex.apache.org > Betreff: Re: Splitting up Flex and Air? > > > > > On 1/28/13 12:25 AM, "christofer.d...@c-ware.de" < > christofer.d...@c-ware.de> > wrote: > > > Hi, > > > > a while ago a user complained that in my Mavenizer I was deploying > > the Air jars in {fdk-root}/lib to the group > > org.apache.flex.compiler/com.adobe.flex.compiler ... ths is indeed > > not quite correct and I would like to fix this. > > > > All Air sdks except 2.6 contain only adt.jar so I think I'm on the > > safe side, but 2.6 has more libs "baksmali.jar", "smali.jar". So > > would it be safe to hard-code these three jars and to place them in > > "com.adobe.air.compiler", or would this have negative side-effects? > > > I don't know what those jars do. If they come from the Adobe AIR SDK > download then unless you have a redistribution agreement with Adobe, > it is technically not allowed for these jars to be in FlexMojos > distribution. > > That's why in the Apache Flex Maven utilities you promised to write > that download utility that requires the user accept the license and > then get the stuff from Adobe. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
