Ok, yeah sorry I meant build system, where downloading deps was one. So how is maven different from gradle, that everybody is converting to from ANT?
It seems I am getting sucked into this project again from some unknown energy, so I am trying to learn some stuff like this. ;-) Mike On Fri, May 8, 2015 at 11:42 AM, Christofer Dutz <christofer.d...@c-ware.de> wrote: > > Actually no ... that's about 20% of what Maven is. > It's more an inversion of control for building applications. Each part of > your application runs through the same phases: > - generate sources > - compile > - compile-tests > - run-tests > - package > - run integration-tests > - install > - deploy > (Simple view) > Now maven has defaults that that know when to do what. If you need > something outside the default, you simply configure what you want > differently. > The great thing is that there are certain standards and these usually > apply to any maven project. For example (if you have copied the > maven-extension to your maven installation) in order to build a FlexJS > application on a clean PC, all you need to have is Java and Maven 3.1 ore > above. As soon as you hit "mvn package" it would download and build your > project without the need to install anything else. No need to set paths, > environment variables, nothing. > > Ok so that's the theory. It's not quite that easy if you need stuff that > hasn't been released yet, but If we had released FlexJS, Falcon and I had > released the final version of Flexmojos 7.1.0 it would be that easy. > > Chris > > ________________________________________ > Von: Michael Schmalle <teotigraphix...@gmail.com> > Gesendet: Freitag, 8. Mai 2015 17:06 > An: dev@flex.apache.org > Betreff: Re: [Falcon] Problems building Falcon > > Honestly, I have never used maven. I get what it is in principle but it's a > dependency retriever right? > > Mike > > On Fri, May 8, 2015 at 10:49 AM, Christofer Dutz < > christofer.d...@c-ware.de> > wrote: > > > Hopefully I'll be able to publish SNAPSHOTS of Falcon and FLexJS in the > > next days so at least with Maven you could start playing around :-) > > > > Chris > > > > ________________________________________ > > Von: Michael Schmalle <teotigraphix...@gmail.com> > > Gesendet: Freitag, 8. Mai 2015 16:44 > > An: dev@flex.apache.org > > Betreff: Re: [Falcon] Problems building Falcon > > > > Those build files are scary huge. :) I couldn't even check out the sdk > > yesterday, git kept barfing on some mustella copying or something. > Strange > > errors I have never seen before in winGIT. > > > > I'm scared to even try getting the sdk and falcon built. :) > > > > Mike > > > > On Fri, May 8, 2015 at 10:31 AM, Christofer Dutz < > > christofer.d...@c-ware.de> > > wrote: > > > > > Hi, > > > > > > > > > after adjusting my FlexJS Maven artifact generation, I wanted to test a > > > build. Unfortunately I needed to re-build falcon for this, but it seems > > > impossible for me to do that via ant. I am always getting > test-failures. > > > > > > > > > I followed your recipe in the other thread, but the falcon "ant all" > > seems > > > to be failing no matter what I try. > > > > > > > > > For example I got this: > > > > > > unit.tests: > > > [mkdir] Created dir: > > > > > > /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/compiler.tests/results > > > [junit] environment property - FLEX_HOME = > > > /Users/christoferdutz/Projects/Apache/Flex/flex-sdk > > > [junit] environment property - PLAYERGLOBAL_HOME = > > > > > > /Users/christoferdutz/Devtools/Apache/apache-flex-4.14.1/frameworks/libs/player > > > [junit] environment property - PLAYERGLOBAL_VERSION = 11.1 > > > [junit] environment property - TLF_HOME = > > > /Users/christoferdutz/Projects/Apache/Flex/flex-tlf > > > [junit] environment property - AIR_HOME = > > > /Users/christoferdutz/Devtools/Adobe/AIR 14.0 > > > [junit] environment property - FLASHPLAYER_DEBUGGER = > > > /Users/christoferdutz/Devtools/Adobe/Flash 14.0/Flash > > > Player.app/Contents/MacOS/Flash Player Debugger > > > [junit] Running > > > org.apache.flex.compiler.internal.css.CSSArrayPropertyValueTests > > > [junit] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time > > > elapsed: 1,512 sec > > > > > > BUILD FAILED > > > /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/build.xml:82: > The > > > following error occurred while executing this line: > > > > > > /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/compiler.tests/build.xml:100: > > > Tests failed > > > > > > > > > But I found out that it must have been related to the > PLAYERGLOBA_VERSION > > > as when I upgraded it to 16.0, I got past this point. > > > > > > Next was that all tests with a "mx" namespace in > > > flex-falcon/compiler.tests/feature-tests/mxml/tags/ seem to fail: > > > > > > [junit] Running mxml.tags.MXMLHTTPServiceTagTests > > > [junit] Generating test: > > > [junit] Compiling test: > > > [junit] > > > > > > -external-library-path=/Users/christoferdutz/Devtools/Apache/apache-flex-4.14.1/frameworks/libs/player/16.0/playerglobal.swc > > > > > > -library-path=/Users/christoferdutz/Projects/Apache/Flex/flex-sdk/frameworks/libs/framework.swc,/Users/christoferdutz/Projects/Apache/Flex/flex-sdk/frameworks/locale/en_US/framework_rb.swc,/Users/christoferdutz/Projects/Apache/Flex/flex-sdk/frameworks/libs/rpc.swc,/Users/christoferdutz/Projects/Apache/Flex/flex-sdk/frameworks/locale/en_US/rpc_rb.swc > > > -namespace= > > > > > > http://ns.adobe.com/mxml/2009,/Users/christoferdutz/Projects/Apache/Flex/flex-sdk/frameworks/mxml-2009-manifest.xml > > > > > > /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/compiler.tests/temp/MXMLHTTPServiceTagTests6077816560368214628.mxml > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'collections' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'logging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'rpc' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time > > > elapsed: 1,051 sec > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'rpc' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'collections' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'collections' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'collections' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'rpc' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'core' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'rpc' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'logging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'messaging' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'styles' > > > [junit] > > > [junit] Error: Unable to resolve resource bundle 'rpc' > > > [junit] > > > > > > BUILD FAILED > > > /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/build.xml:82: > The > > > following error occurred while executing this line: > > > > > > /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/compiler.tests/build.xml:138: > > > Tests failed > > > > > > So I disabled them with "@Ignore". > > > > > > After that I got an error in "SimpleMovie.java" as "flash.simple.Movie" > > > seems to be unavailable, so I commented out even that (leaving nothing > > > useful at all in the class) > > > > > > Now I got even more failures from the flex-compiler-oem package > > > complaining about missing flash.swf package missing. > > > > > > Ok .... so after searching where these stupid flash.swf packages come > > from > > > I found out that it's swfutils which is copied form the Flex SDK .. > > > unfortunately using the variable FLEX_SDK_HOME which I hadn't set > (Didn't > > > read that it was needed) unfortunately this created an empty "swfutils" > > > directory and the next time I built the stuff wasn't copied (the check > > > tests if the directory exists, not if it contains content) ... so after > > > several hours I finally managed to build being even more fed-up with > Ant. > > > > > > So In the end ... I had a too old playerglobal version, I didn't have > the > > > FLEX_SDK_HOME variable set und there were actually only 3 Tests that > > didn't > > > work. We have to improve here. Especially implementing some checks if > at > > > least all variables are set and the minimum requirements are meet. > > > > > > Chris > > > > > > > > >
