incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS <webdoubl...@hotmail.com>
Subject RE: Flex Maven FDK Generator RC1
Date Mon, 24 Sep 2012 15:24:26 GMT
"I am planning on creating something similar to deploy to Artifactory (I
haven't checked, if I even need to implement a separate tool)"

I did it in a way is independent of repository manager you use, it
internally uses the deploy goal.

-----Original Message-----
From: christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de] 
Sent: Monday, September 24, 2012 12:46 PM
To: flex-dev@incubator.apache.org
Subject: AW: Flex Maven FDK Generator RC1

Hi Carlos,

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 them.

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 on the structure.
My FDKs are my opinion on an ideal structure but I would be glad to adjust
if someone has any objections.

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.

Chris



-----Ursprüngliche 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

Hi Chris,

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.

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?

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.

Great work! :)




2012/9/24 christofer.dutz@c-ware.de <christofer.dutz@c-ware.de>

> Hi,****
>
> ** **
>
> 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.****
>
> ** **
>
> 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).****
>
> You should be able to compile using Velos famous 
> iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosForStopWorking<ht
>
tp://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0-RC2/com
pile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosForS
topWorking>configuration option do disable this check (
http://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0-RC2/c
ompile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosFo
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.****
>
> ** **
>
> Things that are different from Velos Deployments:****
>
> ** **
>
> **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)****
>
> **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)****
>
> **3.       **Adobe FDKs are under "com.adobe.flex" and Apache FDKs are
> under "org.apache.flex"****
>
> **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.****
>
> **5.       **There is no longer a "framwework-config-zip", instead there
> 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)****
>
> **6.       **If a library in the framework has a matching "rsl" or "swz"
> 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 version.
> Deploying them with the version of the FDK breaks the ability to load 
> the SWZ files from an Adobe server)****
>
> ** **
>
> I think that was the major stuff ;-)****
>
> ** **
>
> 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.****
>
> ** **
>
> 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****
>
> ** **
>
> [image: Beschreibung: 
> 788335]<http://www.benchpark.com/788335/kundenzufriedenheit.htm>
> ****
>
>    IT- und
> Systemhäuser<http://www.benchpark.com/it_und_systemhaeuser.htm>
> ****
>
> ** **
>
> fon:  0 61 51 / 27315 - 61****
>
> fax:  0 61 51 / 27315 - 64****
>
> mobil:  0171 / 7 444 2 33****
>
> email:  christofer.dutz@c-ware.de****
>
> http://www.c-ware.de****
>
> ** **
>
> UStId-Nr. DE195700962****
>
> ** **
>
> ** **
>



--
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid


Mime
View raw message