Ho John,
well I am currently not Aware of anything Special regarding the names. I too am
using FlexUnit for running my test using FM 7.0.0 and I don't have any issues
with this.
One Thing that might be interfering could be if any pom you are using
references a Flex artifact with an Adobe Group Id ... I think I posted a
enforcer plugin config, that should Output warnings wherever such a dependency
(even if transient) is used:
<!--
Prevent the usage of any old adobe flex artifacts.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>1.3.1</version>
<executions>
<execution>
<id>enforce-banned-dependencies</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<bannedDependencies>
<excludes>
<exclude>com.adobe.flex</exclude>
</excludes>
</bannedDependencies>
</rules>
<fail>true</fail>
</configuration>
</execution>
</executions>
</plugin>
Regarding the Air Support ... well I am currently not Aware of any Problems
building Air applications with Flexmojos.
If there are, it would be good if you could provide me with some more Infos.
What a lot of People were complaining on the old FM Mailinglist (as Long as it
existed) was that they wanted Support to utilize the native packaging types for
delivering air applications to Android and iOs devices. This is what I'm
talking about. I guess the captive runtime fits into the same drawer as this
would be the native packaging for Windows Desktops (If I am correct)
Chris
________________________________________
Von: john gardiner <jwegardi...@gmail.com>
Gesendet: Montag, 6. Januar 2014 23:31
An: users@flex.apache.org
Betreff: Re: AW: AW: AW: New Flexmojos 7.0.0-SNAPSHOT available
Hi Chris,
I also successfully ported to FlexMojos 6.0.1 with FDK 4.11.0.20131017 and
am close with FlexMojos 7.0.0-SNAPSHOT and FDK 4.11.0.20131017.
Just a couple of questions:
1). With FM 6.0.1, I have FlexUnit 4.1.0 running. However, using the same
pom.xml with FlexMojos 7.0.0-SNAPSHOT I get the following console output:
"[INFO] No tests to run.
[INFO] Surefire report directory: C:\FM7.0.0\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0"
This is the entry class I have that works with FM 6.0.1:
"// src/test/flex/Test.as
package
{
import Suite;
[Suite]
[RunWith("org.flexunit.runners.Suite")]
public class Test
{
public var suite:Suite;
}
}"
Is there something fundamental in terms of naming conventions or
configuration of the test phase that has changed with FM 7.0.0 or (more
likely) have I misunderstood something here?
2). Also, by...
"After this initial commit, I will concentrate on Air for Mobile support."
...do you actually mean...
"After this initial commit, I will concentrate on Air support."
...or is there actually a specific reason for currently focusing on mobile?
Either way, I would definitely like to +1 "Captive Runtime" for Air
Desktop...
"There are variations based on the store type (different formats are
supported other than pkcs12), and there are additional supported target
types (desktop captive runtimes, other ipa types for iOS)."
I know "Captive Runtime" is absolutely crucial for my employer (and has also
been crucial for a number of previous employers). Plus, I am really keen to
experiment with using Flexmojos in conjunction with the NSIS plugin
http://mojo.codehaus.org/nsis-maven-plugin/usage.html as a solution. Could
be quite powerful!
John
--
View this message in context:
http://apache-flex-users.2333346.n4.nabble.com/New-Flexmojos-7-0-0-SNAPSHOT-available-tp3798p4358.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
