Just a few things so that we are all on the same page. I mavenized skd 4.1.0.16076A and uploaded to my artifactory as well as copied into my .m2/repository folder. When I set the flex.version to 4.1.016076A I get all sorts of errors of it not being found/recognized etc.
I also mavenized sdk 4.6.0.23201 and everything works perfectly when I do that. (only problem is I'm not allowed to use 4.6 cause I have to target flashplayer 10.1) All of this stems from our initial question here: http://stackoverflow.com/questions/18505129/how-do-i-get-flexunit-flexmojos-and-mockolate-to-work-together The only requirements I have is that I get mockolate, flexunit, and flashplayer 10.1 all working together, and that I'm able to have it run in teamcity through maven :) brought to you by the letters A, V, and I and the number 47 On Tue, Sep 3, 2013 at 5:33 PM, Avi Kessner <[email protected]> wrote: > Thanks, my eyes must have gone blury. You clearly described that in > the migrating to flexmojos 6.0 wiki page, and yet I switched them > around in my actual pom! D'oh! > However, it is still not working. I assume the playerglobal is not > uploaded to the repository in the deploy script? Both my local and > artifactory repositories do not have a pom file for > playerglobal-10.1.swc > > However, in general I feel like I'm missing some crucial bits of > information, so let me write down what I think I understand and then > you can correct me if I'm wrong. > > 1. FlexMojos uses ${flex.version} as a variable in it's pom > heirachy. When I set <flex.version>blah</flex.version> in my pom I am > then defining it for all of flexmojos, except for where it isn't. > 2. For the place where it is not defined, (i.e the compiler) then I > can add my own dependency to the plugin which will override that node > in the relevent flexmojos poms. > > 3. For new versions of Flex SDK, (starting with flex 4.6+??) I need > to mavenize the sdk I am using and upload that to my repository either > manually, or by using the deploy script. > > 4. In addition, I need to also mavenize and upload the playerglobal > for the flash player version I want to use ?? > > 5. For older versions of flex which still reside on the sonotype > repository, I do not need to mavenize the SDK/FDK however, I need to > change the pom to use the correct syntax. > > > > Is this correct? If it is, what is the correct syntax for 5? > > > > brought to you by the letters A, V, and I > and the number 47 > > > On Tue, Sep 3, 2013 at 4:56 PM, [email protected] [via Apache > Flex Users] <[email protected]> wrote: >> Hi, >> >> one Thing I changed in FM6 and in the Mavenizer, is that the FlashPlayer is >> no longer directly coupled. In old FDK Versions Velo provided the >> player-Version was included. I wanted to have the Player loosely coupled and >> therefore I recall that you have to add a dependency to the playerglobal or >> airglobal in the Version you want to the Project. So you should Import the >> playerglobal in Version "${flex.target.player.version}" without any >> classifier and completely remove the flash.classifier variable. >> >> Chris >> >> ________________________________________ >> Von: Frédéric THOMAS [[hidden email]] >> Gesendet: Dienstag, 3. September 2013 15:42 >> An: [hidden email] >> Betreff: RE: AW: AW: how to setup and use maven-flex-plugin >> >> Sorry for the formatting btw, pay attention to use the right version of the >> flex sdk you're using, etc.. >> I took that from an old project made for FM 3.8 Flex 4.5.0.17855 >> >> It is possible you won't have the exact same dependencies for your version >> depending as well of what you need. >> >> -----Message d'origine----- >> De : Frédéric THOMAS [mailto:[hidden email]] >> Envoyé : mardi 3 septembre 2013 15:34 >> À : [hidden email] >> Objet : RE: AW: AW: how to setup and use maven-flex-plugin >> >> Ah ok, so, I guess, either you mavenize the SDK with the mavenizer and then >> use this one or you add each individual dependency under the dependency tag >> of your module. >> >> Ex: >> >> >> <flex.version>4.1.0.16076A</flex.version> >> <flex.theme.version>4.5.0.18623</flex.theme.version> >> <!-- <flex.version>4.5.1.21328</flex.version> --> >> <flex.data.version>4.1.0.16076A</flex.data.version> >> >> <flex.automation.version>4.1.0.16076A</flex.automation.version> >> <flash.classifier>10.2</flash.classifier> >> <flex.sdk.classifier>en_US</flex.sdk.classifier> >> >> <flex.target.player.version>10.1.0</flex.target.player.version> >> >> <!-- Adobe --> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>halo</artifactId> >> <classifier>theme</classifier> >> <version>${flex.theme.version}</version> >> <type>swc</type> >> <scope>theme</scope> >> </dependency> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>spark</artifactId> >> <version>${flex.theme.version}</version> >> <classifier>theme</classifier> >> <type>css</type> >> <scope>theme</scope> >> </dependency> >> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>playerglobal</artifactId> >> <version>${flex.version}</version> >> <classifier>${flash.classifier}</classifier> >> <type>swc</type> >> </dependency> >> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>flex-framework</artifactId> >> <version>${flex.version}</version> >> <type>pom</type> >> <exclusions> >> <exclusion> >> >> <groupId>com.adobe.flex.framework</groupId> >> >> <artifactId>playerglobal</artifactId> >> </exclusion> >> <exclusion> >> >> <groupId>com.adobe.flex.framework</groupId> >> >> <artifactId>flash-integration</artifactId> >> </exclusion> >> <exclusion> >> >> <groupId>com.adobe.flex.framework</groupId> >> >> <artifactId>utilities</artifactId> >> </exclusion> >> </exclusions> >> </dependency> >> >> <!-- Automation --> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>automation_spark</artifactId> >> >> <version>${flex.automation.version}</version> >> <type>swc</type> >> </dependency> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>automation</artifactId> >> >> <version>${flex.automation.version}</version> >> <type>rb.swc</type> >> </dependency> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>automation</artifactId> >> >> <version>${flex.automation.version}</version> >> <type>swc</type> >> </dependency> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>automation_agent</artifactId> >> >> <version>${flex.automation.version}</version> >> <type>rb.swc</type> >> </dependency> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>automation_agent</artifactId> >> >> <version>${flex.automation.version}</version> >> <type>swc</type> >> </dependency> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>automation_dmv</artifactId> >> >> <version>${flex.automation.version}</version> >> <type>swc</type> >> </dependency> >> >> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>datavisualization</artifactId> >> <version>${flex.data.version}</version> >> <type>swc</type> >> </dependency> >> >> <dependency> >> <groupId>com.adobe.flex.framework</groupId> >> <artifactId>datavisualization</artifactId> >> <version>${flex.data.version}</version> >> <!-- >> <classifier>${flex.sdk.classifier}</classifier> --> >> <type>rb.swc</type> >> </dependency> >> >> -----Message d'origine----- >> De : akessner [mailto:[hidden email]] Envoyé : mardi 3 septembre 2013 15:08 >> À : [hidden email] Objet : Re: AW: AW: how to setup and use >> maven-flex-plugin >> >> Right, sorry I wasn't clear I had done that. >> It seems that part of the problem is that I'm only able to find 4.1sdk >> online to download which has an A in the version name... so whats in my >> local repo is actually 4.1.0.16076A >> >> So I have framework-4.1.0.16076A.pom but I am missing and maven can >> not find fraemwork-4.1.0.16076.pom >> >> Why oh why do so many of our users still have flash player 10.3? argh! >> brought to you by the letters A, V, and I and the number 47 >> >> >> On Tue, Sep 3, 2013 at 3:47 PM, Frédéric THOMAS [via Apache Flex Users] >> <[hidden email]> wrote: >> >>> You should remove the compiler dependency from the general >>> dependencies of your module but keep it in the dependencies of the FM >>> plugin as I indicated to you before. >>> >>> -----Message d'origine----- >>> De : akessner [mailto:[hidden email]] >>> Envoyé : mardi 3 septembre 2013 14:31 >>> À : [hidden email] >>> Objet : Re: AW: AW: how to setup and use maven-flex-plugin >>> >>> My bad, it actually doesn't have that pom... I can create it >>> manually, but any ideas why it's missing? >>> brought to you by the letters A, V, and I and the number 47 >>> >>> >>> On Tue, Sep 3, 2013 at 3:26 PM, Avi Kessner <[hidden email]> wrote: >>> >>>> Maven is alternating between giving me the error that it can't find >>>> the player global and that it can't find framework:pom:... >>>> >>>> [ERROR] Failed to execute goal >>>> net.flexmojos.oss:flexmojos-maven-plugin:6.0.1:compile-swf >>>> (default-compile-swf) on project helloWorld3: >>>> java.lang.reflect.InvocationTargetException: Failed to resolve >>>> artifact com.adobe.flex:framework:pom:4.1.0.16248 -> [Help 1] [ERROR] >>>> >>>> However, I see these things in my repository... >>>> brought to you by the letters A, V, and I and the number 47 >>>> >>>> >>>> On Tue, Sep 3, 2013 at 3:12 PM, Avi Kessner <[hidden email]> wrote: >>>>> This is sending me into an infinite loop :) I've added the compiler >>>>> to the dependency inside the plugin. But now I'm getting new >>>>> errors. >>>>> brought to you by the letters A, V, and I and the number 47 >>>>> >>>>> >>>>> On Tue, Sep 3, 2013 at 2:59 PM, Frédéric THOMAS [via Apache Flex >>>>> Users] <[hidden email]> wrote: >>>>>> Just answered here >>>>>> >>>>>> http://apache-flex-users.2333346.n4.nabble.com/how-to-setup-and-use >>>>>> -maven-flex-plugin-td1491i20.html#a2518 >>>>>> >>>>>> ________________________________ >>>>>> If you reply to this email, your message will be added to the >>>>>> discussion >>>>>> below: >>>>>> >>>>>> http://apache-flex-users.2333346.n4.nabble.com/how-to-setup-and-use >>>>>> -maven-flex-plugin-tp1491p2519.html >>>>>> To unsubscribe from how to setup and use maven-flex-plugin, click here. >>>>>> NAML >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-flex-users.2333346.n4.nabble.com/how-to-setup-and-use-ma >>> ven-flex-plugin-tp1491p2524.html Sent from the Apache Flex Users >>> mailing list archive at Nabble.com. >>> >>> >>> ________________________________ >>> If you reply to this email, your message will be added to the >>> discussion >>> below: >>> http://apache-flex-users.2333346.n4.nabble.com/how-to-setup-and-use-ma >>> ven-flex-plugin-tp1491p2525.html To unsubscribe from how to setup and >>> use maven-flex-plugin, click here. >>> NAML >> >> >> >> >> -- >> View this message in context: >> http://apache-flex-users.2333346.n4.nabble.com/how-to-setup-and-use-maven-flex-plugin-tp1491p2526.html >> Sent from the Apache Flex Users mailing list archive at Nabble.com. >> >> ________________________________ >> If you reply to this email, your message will be added to the discussion >> below: >> http://apache-flex-users.2333346.n4.nabble.com/how-to-setup-and-use-maven-flex-plugin-tp1491p2536.html >> To unsubscribe from how to setup and use maven-flex-plugin, click here. >> NAML -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/how-to-setup-and-use-maven-flex-plugin-tp1491p2543.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
