pshirshov/antennae

Automatically exported from code.google.com/p/antennae

antennae's Issues

testing on Linux doesn't work unless opt1 and opt2 are removed

I set up a build environment on Linux and got my application and its tests
to build but "ant test" caused:
     [exec] Error: Invalid SWF file name

     [exec] Usage: flashplayer [OPTION]... [SWF_FILE]...
     [exec] Options:
     [exec]   -h, --help            Display this help and exit
     [exec]   -root                 Use root window for xscreensaver
     [exec]                         [SWF_FILE] required in this mode
     [exec]   -window-id <id>       Window ID for xscreensaver-demo preview

     [exec] Report bugs to <[email protected]>.
     [exec] Result: 255

I found that removing these 2 lines from build-common-targets.xml made the
test work as expected:
                    <arg value="${test.flexunit2.opt1}" />
                    <arg value="${test.flexunit2.opt2}" />

I do realize that these are likely needed for other OSes and configurations
but there were no options being set for Linux (as per ant -v test).

Original issue reported on code.google.com by [email protected] on 7 Oct 2007 at 6:58

Building Antennae error

What steps will reproduce the problem?
1. followed the Cookbook instructions
2. set flex.dir=C:/Program Files/Adobe/Flex Builder 3/sdks/3.0.0 in build-
user.properties
3. Build Antennae with Ant

What is the expected output? What do you see instead?

Buildfile: E:\a faire\dev\tools\Antennae\build.xml
build:
   [subant] Entering directory: E:\a faire\dev\tools\Antennae\tutorial
build:
   [subant] Entering directory: E:\a faire\dev\tools\Antennae\tutorial\app2
init:
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\app2\bin
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\app2
\bin\generated
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\app2
\bin\classes
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\app2
\bin\swc
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\app2
\bin\swf
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\app2
\bin\asdoc
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\app2
\bin\stage
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\app2
\bin\dist
flex-application-check:
flex-application-copy:
     [copy] Copying 1 file to E:\a faire\dev\tools\Antennae\tutorial\app2
\bin\swf
flex-application:
     [java] Loading configuration file C:\Program Files\Adobe\Flex Builder 
3\sdks\3.0.0\frameworks\flex-config.xml
     [java] bin/swf//Main.swf (152397 bytes)
build:
   [subant] Leaving directory: E:\a faire\dev\tools\Antennae\tutorial\app2
   [subant] Entering directory: E:\a faire\dev\tools\Antennae\tutorial\test
init:
    [mkdir] Created dir: E:\a faire\dev\tools\Antennae\tutorial\test\bin
    [mkdir] Created dir: E:\a 
faire\dev\tools\Antennae\tutorial\test\bin\generated
    [mkdir] Created dir: E:\a 
faire\dev\tools\Antennae\tutorial\test\bin\classes
    [mkdir] Created dir: E:\a 
faire\dev\tools\Antennae\tutorial\test\bin\swc
    [mkdir] Created dir: E:\a 
faire\dev\tools\Antennae\tutorial\test\bin\swf
    [mkdir] Created dir: E:\a 
faire\dev\tools\Antennae\tutorial\test\bin\asdoc
    [mkdir] Created dir: E:\a 
faire\dev\tools\Antennae\tutorial\test\bin\stage
    [mkdir] Created dir: E:\a 
faire\dev\tools\Antennae\tutorial\test\bin\dist
create-test-suite-check:
create-test-suite:
     [echo] Updating bin/generated/FlexUnitAllTests.as
     [copy] Copying 1 file to E:\a 
faire\dev\tools\Antennae\tutorial\test\bin\generated
flex-application-check:
flex-application-copy:
flex-test-application:
     [java] command line: Error: default arguments may not be interspersed 
with other options
     [java] Use 'mxmlc -help' for information about using the command line.
   [subant] Leaving directory: E:\a faire\dev\tools\Antennae\tutorial\test
   [subant] Leaving directory: E:\a faire\dev\tools\Antennae\tutorial

BUILD FAILED
E:\a faire\dev\tools\Antennae\tools\build-master-targets.xml:43: The 
following error occurred while executing this line:
E:\a faire\dev\tools\Antennae\tools\build-common-tasks.xml:279: The 
following error occurred while executing this line:
E:\a faire\dev\tools\Antennae\tools\build-master-targets.xml:43: The 
following error occurred while executing this line:
E:\a faire\dev\tools\Antennae\tools\build-common-tasks.xml:279: The 
following error occurred while executing this line:
E:\a faire\dev\tools\Antennae\tools\build-common-targets.xml:354: The 
following error occurred while executing this line:
E:\a faire\dev\tools\Antennae\tools\build-common-tasks.xml:54: Java 
returned: 1

What version of the product are you using? On what operating system?
1.2.0, windows, flex builder 3.0

Please provide any additional information below.
I'm stuck ;)

Original issue reported on code.google.com by [email protected] on 21 May 2008 at 8:48

Assets in SWC Files

What steps will reproduce the problem?
1. compile a swc using flex2-library task.

What is the expected output? What do you see instead?
- expect assets to be included in the swc, but only the assets with Embed 
tages are included

What version of the product are you using? On what operating system?


Please provide any additional information below.

Original issue reported on code.google.com by jamesghandour on 13 Feb 2008 at 4:26

Flex targets should be prefixed flex- instead of flex2-

The current naming of Flex targets using a prefix of "flex2-" is
misleading. True, these tasks aren't going to be backwards compatible to
Flex1, but Flex1 is a dinosaur now. The actual tools used for Flex 2 and
Flex 3 are quite similar, so it would be better to use a "flex-" prefix for
targets, and "${flex.*}" instead of "${flex2.*}" for property names.

The VisualFlexUnit project has already done this.

This change could be made so that "flex2-" and "${flex2.*}" are deprecated
but still functional in the next release of Antennae, allowing existing
build scripts to work and giving developers some time to adjust.

Original issue reported on code.google.com by [email protected] on 11 Jan 2008 at 5:51

new properties for mxmlc task needed for integration with blazeDS and LCDS

What is the expected output? What do you see instead?
Expected is to be able to use context-root and services in the mxmlc task.

Please add it to the next release:

I updated the build-common-tasks:
<macrodef name="mxmlc" description="">
        <attribute name="src" />
        <attribute name="dest" />
        <attribute name="src.path" default="${src.flex.dir}" />
        <attribute name="lib.path.id" default="flex.lib.path" />
        <attribute name="options" default="${flex.mxmlc.options}" />
        <attribute name="config" default="${flex.config}" />
        <attribute name="context-root"
default="${flex.mxmlc.compiler.context-root}" />
        <attribute name="services" default="${flex.mxmlc.compiler.services}"/>
        <sequential>
            <fail>
                <condition>
                    <not>
                        <isreference refid="@{lib.path.id}" />
                    </not>
                </condition>
            </fail>

            <pathconvert property="_mxmlc.lib.files" refid="@{lib.path.id}"
pathsep="," />
            <condition property="_mxmlc.libpath"
value='-library-path+="${_mxmlc.lib.files}"' else="">
                <not>
                    <equals arg1="" arg2="${_mxmlc.lib.files}" trim="true" />
                </not>
            </condition>

            <java jar="${flex.mxmlc.jar}" dir="." fork="true"
failonerror="true">
                <jvmarg value="-Xmx512m" />
                <arg line="@{options} ${_mxmlc.libpath}" />
                <arg value="+flexlib=${flex.frameworks.dir}" />
                <arg value="-load-config=@{config}" />
                <arg value="-source-path=@{src.path}" />
                <arg value="-file-specs=@{src}" />
                <arg value="-output=@{dest}" />
                <arg value="-compiler.context-root=@{context-root}"/>
                <arg value="-compiler.services=@{services}"/>
            </java>
        </sequential>
    </macrodef>

build-common-targets:

<target name="flex-application"
depends="init,flex-application-check,flex-application-copy"
        unless="${project.swf}.compiled" description="Compile the application">
        <mxmlc src="${src.flex.dir}/${project.flex.application}"
            dest="${build.mxmlc.dir}/${project.swf}"
            services="${flex.mxmlc.compiler.services}"
            context-root="${flex.mxmlc.compiler.context-root}">
        </mxmlc>
    </target>

and build-common-properties:
<property name="flex.mxmlc.compiler.services" value=""/>
    <property name="flex.mxmlc.compiler.context-root=/seamserver" value=""/>

Original issue reported on code.google.com by [email protected] on 4 Nov 2008 at 12:22

Antennae extensions / refinements

I'm including a number of additions that we have made to the Antennae
system, for consideration into the Antennae system.

Basic feature description:

1) Bump the required ant version to 1.7 (current system requires 1.65+).
This allows for a few more simplified constructs.

2) Add a $foo_version pattern. Ant, Flex, Antennae, and Java would all have
a version property. So the definition for flex.dir becomes <property
name="flex.dir" value="${root.build.dir}/flex/${flex.version}" />. This
allows for easy switching of versions (especially for Flex SDKs) like this:

someRoot/flex/2.0.1.HF1
someRoot/flex/3.0.0.B2
someRoot/flex/3.0.0.RC3

etc.

3) Adding some staging support for Flex and Tomcat distributions

Added targets of war-stage, war-dist, webapp-stage, java-stage

4) Added unified Flex html-template support.

Flex 2.0.1 stored its templates in a different relative folder than Flex3
SDKs. The $flex2.templates.dir conditional property takes care of this
different path structure. Just set the $flex.version correctly, and
everything just works.

5) Extend flex-application target to support forced linkage of SWCs (for
resources). See the flex2-application-with-forcelink target for more details.

6) Added html-wrapper macrodef. To help generate HTML templates.

Feel free to add, reject, or point and laugh. :)

Original issue reported on code.google.com by [email protected] on 27 Feb 2008 at 4:58

Attachments:

• build-eui-imports.xml
• build-eui-master-targets.xml
• build-eui-properties.xml
• build-eui-targets.xml
• build-eui-tasks.xml

Add support for compiling resource modules

Currently the mxmlc marco cannot be used for compiling resource modules 
because it includes the file-specs param.

Original issue reported on code.google.com by jamesghandour on 11 Mar 2008 at 1:38

Sometimes ARC Report Server exits with error before reporting Test Results

What steps will reproduce the problem?
1. Run an Air Flexunit App with Antennae

What is the expected output? What do you see instead?

The expected output would be either a informational failure message,
including the number of successful and failed tests, or a failed build
reporting the reason why.

Instead, the ARC Unit Test Report server sometimes doesn't receive
notification of the results.  The Report Server java process exits with
code 1.  The build fails because of this return code, but doesn't give any
useful information.

What version of the product are you using? On what operating system?

Using trunk on Linux.

Please provide any additional information below.

This doesn't seem to be reproducible on mac.  But is very reliable on RHEL.
 The fix is to call the optional AIR callback method at the end of the
results printing handler.

# svn diff
arc-flexunit/flex/com/allurent/flexunit/framework/ARCResultPrinter.as
Index: arc-flexunit/flex/com/allurent/flexunit/framework/ARCResultPrinter.as
===================================================================
--- arc-flexunit/flex/com/allurent/flexunit/framework/ARCResultPrinter.as
(revision 48)
+++ arc-flexunit/flex/com/allurent/flexunit/framework/ARCResultPrinter.as
(working copy)
@@ -154,10 +154,6 @@
             var runTime:int = endTime - _testsStartTime;
             prepareReport(runTime);
             sendReport();
-            if (_callbackOnAllTestsEnd != null)
-            {
-                _callbackOnAllTestsEnd();
-            }
         }

         /**
@@ -355,6 +351,12 @@

             _theSocket.close();
             fscommand("quit", "");
+
+            // Finally, call any callback once we've reported to the
report server.
+            if (_callbackOnAllTestsEnd != null)
+            {
+                _callbackOnAllTestsEnd();
+            }
         }
     }
 }

Original issue reported on code.google.com by [email protected] on 23 Jan 2009 at 8:44

adt certificate usage syntax

The syntax to use a certificate with adt is incorrect in the build-common-
tasks.xml.

It should be more along the lines of this...
        <arg value="-storetype" />
        <arg value="PKCS12" />
                <arg value="-keystore" />
                <arg value="@{cert}" />
                <arg value="-storepass" />
                <arg value="@{cert-pwd}" />

you will probably want to add another variable for the storetype value, so 
that it is user-customizable.

Original issue reported on code.google.com by jamesghandour on 13 Feb 2008 at 4:28

Test AIR Apps

Although there is a way to build air application, there is currently no 
way to test them use antennae.

Original issue reported on code.google.com by jamesghandour on 11 Mar 2008 at 1:39

fearure request: add fcsh support

Hi,

first of all thanx for the really great build system. It scales nicely and 
allows for complex dependencies wich i didn't see 
anywhere else.

A proposed improvement. It would be really nice if the anteannae build scripts 
could use the flex compiler shell in some way. 
Im building a complex project with modules and different css files. The build 
system becomes very slow compared to flex 
builder. 

This is because for each compile the compiler has to be started up, which is 
slow.

It would be awesome if antannae could make use of the flex compiler shell. Them 
the compiler would remain in memory and 
incremental compiles are possible speading up the build system in a great way.

There are some opensource solutions that could give a good start but im not a 
java programmer so for me it's a bit daunting.
see:
http://labs.adobe.com/wiki/index.php/Flex_Compiler_Shell
http://labs.adobe.com/wiki/index.php/Talk:Flex_Compiler_Shell
http://sourceforge.net/projects/fcshwrapper/

would be cool!

Original issue reported on code.google.com by [email protected] on 1 May 2009 at 2:40