Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.189 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Mon, 24 Sep 2012 23:14:30 -0700
Subject: Re: AW: AW: Flex Maven FDK Generator RC1
Thread-Topic: AW: AW: Flex Maven FDK Generator RC1
Thread-Index: Ac2aSSCu3H8GO4I5SZKhyCMYkPDhagAAUh3AAAow9eAAG60sEAAAyQ3a
Message-ID: <CC8699D6.46625%aharui@adobe.com>
In-Reply-To: 
 <66E38C42347D6446BF7FCB22C3D3878072DDC95B92@ECCR06PUBLIC.exchange.local>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.13.0.120411
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Chris,

Who is the "you" that runs the generator: the customer who wants to build
and app with an FDK or the Apache Flex release manager?  If the generator
bundles Adobe binaries, then without an distribution agreement, you can't
publish the FDK for download by the customer.

I don't know if Velo had an agreement or if Adobe never looked or cared, bu=
t
I certainly can't put Apache in a tenuous position.  It will also be
"harder" for Apache to want to distribute binaries on Adobe's behalf since
Apache is primarily about "source" (at least for now).

Again, I am not very knowledgeable about Maven, but I thought that folks
wanted Apache Flex releases to pull down Adobe FlashPlayer and AIR SDKs as
Maven dependencies as well so they didn't have to be pre-installed by the
customer.

-Alex


On 9/24/12 10:56 PM, "christofer.dutz@c-ware.de" <christofer.dutz@c-ware.de=
>
wrote:

> Hi Alex,
>=20
> Currently the Generator works in a way that you download the Flex/Air SDK=
s the
> normal way and place them into a special directory structure. After that =
you
> run the generator and that copies the files, generates the poms and packa=
ges
> the themes automatically. I think this was should be no problem at all. A=
fter
> all every user has to officially download the SDKs the ordinary way hereb=
y
> accepting the license from Adobe.
>=20
> Somehow there must have been some agreement between Velo and Adobe, as he
> seems to have had the permission to publish the Flex SDKs in a Maven repo=
.
> Perhaps Apache will be able to get a similar agreement and would be allow=
ed to
> publish the artifacts.
>=20
> Chris
>=20
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Montag, 24. September 2012 18:40
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: Flex Maven FDK Generator RC1
>=20
> Chris,
>=20
> IMO, even a download link to the actual Adobe binaries stored on a non-Ad=
obe
> site is not legal.  I believe that any final structure will require
> downloading Adobe binaries from Adobe or some third party that has a lice=
nse
> to do so.  Imagine this was an MP3 file:  you are restricted from sharing
> music without permission of the artist.
>=20
> What would be the minimum change Adobe would need to allow you to get the
> Adobe stuff from Adobe?  Would I just need to place pom.xml files next to=
 the
> zips for AIR SDK and Player?  If so, I will look into getting that to hap=
pen.
> What would go in the pom.xml files?
>=20
>=20
> On 9/24/12 4:50 AM, "christofer.dutz@c-ware.de" <christofer.dutz@c-ware.d=
e>
> wrote:
>=20
>> Hi Carlos,
>>=20
>> I could whip up a "dummy" version of my FDKs replacing the binary
>> artifacts with empty placeholders of the same name. This way there
>> shouldn't be any legal issues with me publically making Adobe stuff
>> downloadable.
>> The other alternative would be that everyone interested in the
>> Structure to contact me and I'll give them the download link (I just
>> don't want to get into Trouble with Adobe).
>>=20
>> Chris
>>=20
>>=20
>>=20
>> -----Urspr=FCngliche Nachricht-----
>> Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im
>> Auftrag von Carlos Rovira
>> Gesendet: Montag, 24. September 2012 13:32
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: Flex Maven FDK Generator RC1
>>=20
>> Hi Chris,
>>=20
>> you're completly right. In order to get this milestone we need to
>> discuss project structure to get parent/child, and so on...
>>=20
>> I think a new [Discuss] thread should be open ASAP to see everyone
>> opinion about this.
>>=20
>>=20
>>=20
>>=20
>> 2012/9/24 christofer.dutz@c-ware.de <christofer.dutz@c-ware.de>:
>>> Hi Carlos,
>>>=20
>>> I was hoping that Apache would start publishing their FDKs in a
>>> Mavenized form. With the Tool it should be almost no work at all.
>>> Frederic added a tool to deploy the generated artifacts to Nexus, I
>>> am planning on creating something similar to deploy to Artifactory (I
>>> haven't checked, if I even need to implement a separate tool). Using
>>> these it should be easy to integrate them into the release build. If
>>> any maven/ant plugin adapters are needed I would be glad to provide the=
m.
>>>=20
>>> The first step to mavenizing Flex is do decide on the structure of
>>> the project. I think my Generator is a first step in this direction
>>> and that's one of the reasons why I would like to open the discussion o=
n the
>>> structure.
>>> My FDKs are my opinion on an ideal structure but I would be glad to
>>> adjust if someone has any objections.
>>>=20
>>> The poms are very simple. They don't contain the maven config needed
>>> to build. They even don't contain the dependency information needed to
>>> build.
>>> In order to use the poms to build Flex in Maven it would make it
>>> necessary to add the parent/child module config stuff, the plugin
>>> configuration stuff, the dependencies and so on.
>>> But even if it would not be a simple "drop in the poms" process, I
>>> think it shouldn't be that hard.
>>>=20
>>> Chris
>>>=20
>>>=20
>>>=20
>>> -----Urspr=FCngliche Nachricht-----
>>> Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im
>>> Auftrag von Carlos Rovira
>>> Gesendet: Montag, 24. September 2012 12:24
>>> An: flex-dev@incubator.apache.org
>>> Betreff: Re: Flex Maven FDK Generator RC1
>>>=20
>>> Hi Chris,
>>>=20
>>> this sounds very good. The point 5 should be the solution to the
>>> problem we had with themes. I would like to have access to the link in =
order
>>> to test it.
>>>=20
>>> btw, if this works and we finaly have a working process to have
>>> mavenized flex artifacts...could this be integrated in the build
>>> process to apache flex to have official apache flex maven artifacts?
>>>=20
>>> Going one step further... would be possible to create pom.xml for
>>> each apache flex project to create flex maven artificats from now on?
>>> This could generate maven flex artifacts from source code with
>>> jenkins as part of the normal apache flex sdk generation process and
>>> could be deployed to apache maven official repo.
>>>=20
>>> Great work! :)
>>>=20
>>>=20
>>>=20
>>>=20
>>> 2012/9/24 christofer.dutz@c-ware.de <christofer.dutz@c-ware.de>
>>>=20
>>>> Hi,****
>>>>=20
>>>> ** **
>>>>=20
>>>> I just wanted to inform you, that I have somewhat finished my Flex
>>>> FDK Generator. With this tool you should be able to generate
>>>> Mavenized FDKs from any existing Flex FDK (Apache or Adobe) and Air
>>>> SDK.****
>>>>=20
>>>> ** **
>>>>=20
>>>> In order to use the new FDKs with Flexmojos 6.x I still have to
>>>> change some stuff in Flexmojos 6.x (The framework.swc now has the
>>>> version of the swz and this sometimes differs from the FDK version
>>>> and hereby from the compiler.jar version).****
>>>>=20
>>>> You should be able to compile using Velos famous
>>>> iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosForStopWorking<
>>>> h
>>>> t
>>>> tp://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0
>>>> -RC2/com=20
>>>> pile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexm
>>>> ojosForS
>>>> topWorking>configuration option do disable this check (
>>>> http://repository.sonatype.org/content/sites/maven-sites/flexmojos/4
>>>> .0-RC2/c=20
>>>> ompile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFle
>>>> xmojosFo
>>>> rStopWorking).
>>>> Even if you don't want to actually use Flexmojos 6.x it would be
>>>> great to get some feedback on the deployment structure. Currently it
>>>> would be easy to change things . as soon as Deployments are
>>>> available, this would be hard to fix.****
>>>>=20
>>>> ** **
>>>>=20
>>>> Things that are different from Velos Deployments:****
>>>>=20
>>>> ** **
>>>>=20
>>>> **1.       **Flash player stuff is now in "com.adobe.flash.framework"
>>>> (The playerglobals are here) and "com.adobe.flash.runtime" (The
>>>> Flashplayer executable binaries are here) (There is no longer any
>>>> "playerglobal-{fdk-version}-{player-version}.swc" artifacts)****
>>>>=20
>>>> **2.       **Air stuff is now in "com.adobe.air.framework" (The
>>>> airglobals are here) (I didn't make it deploy the air runtime as
>>>> this would have been really tricky)****
>>>>=20
>>>> **3.       **Adobe FDKs are under "com.adobe.flex" and Apache FDKs are
>>>> under "org.apache.flex"****
>>>>=20
>>>> **4.       **There are new Artifacts
>>>> "com.adobe.flex:framework:{fdk-version}:pom" which define the
>>>> explicit versions of each library of the FDK and can be used by
>>>> importing this artifact into your projects dependency
>>>> management.****
>>>>=20
>>>> **5.       **There is no longer a "framwework-config-zip", instead the=
re
>>>> is a swc-Theme for every theme of a FDK under
>>>> "com.adobe.flex.framework.themes" (During deployment I use compc to
>>>> compile a SWC from every theme that is not already an SWC theme)****
>>>>=20
>>>> **6.       **If a library in the framework has a matching "rsl" or "sw=
z"
>>>> the versions of these are used to deploy the artifact (generally
>>>> affects "osmf" and "textlayout" but in the A and B versions of
>>>> patched FDKs the versions of "framework" etc. differ from the FDK vers=
ion.
>>>> Deploying them with the version of the FDK breaks the ability to
>>>> load the SWZ files from an Adobe server)****
>>>>=20
>>>> ** **
>>>>=20
>>>> I think that was the major stuff ;-)****
>>>>=20
>>>> ** **
>>>>=20
>>>> If someone wants to have a look at the FDKs, please contact me and
>>>> I'll send you the link to the download (Don't want to publish that
>>>> here). I will continue to make Flexmojos work with my new FDKs as
>>>> soon as that's finished and seems to be working I would like to make
>>>> the Generator publically
>>>> available.****
>>>>=20
>>>> ** **
>>>>=20
>>>> Chris****
>>>>=20
>>>> ** **
>>>>=20
>>>> ** **
>>>>=20
>>>> [ C h r i s t o f e r  D u t z ]****
>>>>=20
>>>> ** **
>>>>=20
>>>> C-Ware IT-Service****
>>>>=20
>>>> Inhaber****
>>>>=20
>>>> Dipl. Inf. Christofer Dutz****
>>>>=20
>>>> Karlstra=DFe. 104, 64285 Darmstadt****
>>>>=20
>>>> ** **
>>>>=20
>>>> [image: Beschreibung:
>>>> 788335]<http://www.benchpark.com/788335/kundenzufriedenheit.htm>
>>>> ****
>>>>=20
>>>>    IT- und
>>>> Systemh=E4user<http://www.benchpark.com/it_und_systemhaeuser.htm>
>>>> ****
>>>>=20
>>>> ** **
>>>>=20
>>>> fon:  0 61 51 / 27315 - 61****
>>>>=20
>>>> fax:  0 61 51 / 27315 - 64****
>>>>=20
>>>> mobil:  0171 / 7 444 2 33****
>>>>=20
>>>> email:  christofer.dutz@c-ware.de****
>>>>=20
>>>> http://www.c-ware.de****
>>>>=20
>>>> ** **
>>>>=20
>>>> UStId-Nr. DE195700962****
>>>>=20
>>>> ** **
>>>>=20
>>>> ** **
>>>>=20
>>>=20
>>>=20
>>>=20
>>> --
>>> Carlos Rovira
>>> Director de Tecnolog=EDa
>>> M: +34 607 22 60 05
>>> F:  +34 912 35 57 77
>>> <http://www.codeoscopic.com>
>>> CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Per=F3n,
>>> 32 Planta 10, Puertas P-Q
>>> 28020 Madrid
>>=20
>>=20
>>=20
>> --
>> Carlos Rovira
>> Director de Tecnolog=EDa
>> M: +34 607 22 60 05
>> F:  +34 912 35 57 77
>> CODEOSCOPIC S.A.
>> Avd. del General Per=F3n, 32
>> Planta 10, Puertas P-Q
>> 28020 Madrid
>=20
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>=20

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui