The groupId is com.adobe.flex (though the underlying code is actually
Apache).  I went through the whole "mavenizer" process.  I thought I did
specify a different version with this fragment in my POM
(where flex.version=4.11.0.201317).
    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>com.adobe.flex</groupId>
                <artifactId>framework</artifactId>
                <version>${flex.version}</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

I saw that 7.0 just came out.  I'm sure I will upgrade, but not today if I
can solve this problem.



On Thu, Apr 17, 2014 at 11:17 AM, Christofer Dutz [via Apache Flex Users] <
[email protected]> wrote:

> You say that you are using Flex 4.11 ... what GroupId are you using?
> Flexmojos 6.x can only work with Flex SDKs if they have the GroupId
> com.adobe.flex
> If you are using org.apache.flex, you need to update to Flexmojos 7.x (I
> just released 7.0.0 two days ago).
>
> The reference to com.adobe.flex is the default FDK Flexmojos 6.0.1 was
> built against. So it uses this if you don't specify a different version.
>
> If you want to use FM6, you need to tell the mavenizer to generate Apache
> FDKs using the Adobe GroupId but I would strongly suggest to use FM 7.0.0
>
>
> Chris
>
> ________________________________________
> Von: dcorbin <[hidden 
> email]<http://user/SendEmail.jtp?type=node&node=6172&i=0>>
>
> Gesendet: Donnerstag, 17. April 2014 17:09
> An: [hidden email] <http://user/SendEmail.jtp?type=node&node=6172&i=1>
> Betreff: Flex Mojos 6.0.1, unusual failure
>
> I recently set up a flex project to be able to build via maven.  It is
> using
> FM 6.0.1, AIR 3.9, Flex 4.11.20131017, and Flash 11.9.  It took a lot of
> work to get everything working correctly, but I got there.  The project
> built fine on both my system and on our Jenkins system.
>
> A recent change (the introduction of the a new ANE) introduced a new
> problem.  I can now build it on my system, but our Jenkins system fails
> because it cannot resolve some of the symbols from the ANE. I've done my
> best to figure out what might be different between the systems that would
> cause this without any success.
>
> I've done "maven -X", and compared all the arguments being passed to the
> compiler.  File system paths are different, and the order of some of the
> parameters varies a little bit, but nothing that seems like it would
> matter.
> The new ANE is clearly listed in as argument -compiler-library-path.
>
> I do get numerous warnings, but I got those before the new ANE was added.
> [WARNING] The POM for com.adobe.flex:compiler:pom:4.6.0.23201 is missing,
> no
> dependency information available
> [WARNING] The POM for com.adobe.flex.compiler:mxmlc:jar:4.6.0.23201 is
> missing, no dependency information available
> [WARNING] The POM for com.adobe.flex.compiler:digest:jar:4.6.0.23201 is
> missing, no dependency information available
> [WARNING] The POM for com.adobe.flex.compiler:optimizer:jar:4.6.0.23201 is
> missing, no dependency information available
> [WARNING] The POM for com.adobe.flex.compiler:asdoc:jar:4.6.0.23201 is
> missing, no dependency information available
> [WARNING] The POM for com.adobe.flex.compiler:swcdepends:jar:4.6.0.23201
> is
> missing, no dependency information available
>
> These dependencies appear to come from
> net.flexmojos.oss:flexmojos-flex-compiler:jar:6.0.1:compile
>
> So, what else should I be looking at?
>
> David Corbin
>
>
>
>
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/Flex-Mojos-6-0-1-unusual-failure-tp6170.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/Flex-Mojos-6-0-1-unusual-failure-tp6170p6172.html
>  To unsubscribe from Flex Mojos 6.0.1, unusual failure, click 
> here<http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=6170&code=ZGNvcmJpbkB6Y29ydW0uY29tfDYxNzB8LTE3MDk3ODQ0Mzg=>
> .
> NAML<http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://apache-flex-users.2333346.n4.nabble.com/Flex-Mojos-6-0-1-unusual-failure-tp6170p6175.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Reply via email to