flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hays Clark (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-35090) As a User, I would like FlexUnit 4.1.0 to support compiler options so I can easily compile more complicated Flash/Flex projects.
Date Fri, 13 May 2016 20:58:12 GMT

     [ https://issues.apache.org/jira/browse/FLEX-35090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hays Clark updated FLEX-35090:
------------------------------
    Description: 
The FlexUnit Ant task does not support compiler options, yet there are some custom forks online
of FlexUnit which have added this support too 4.1.x.  Instead of people having to hunt down
those fork there should be a 4.1.x release which has this support.  This feature should ideally
added to 4.2.x if its does not 'break' any existing functionality.  GradleFX both supports
a 'additionalCompilerOptions' flag, but most FlexUnit tags are singular.  'additionalCompilerOption'
seems like a good match.

Example XML:
{code:title=Example.xml}
        <!-- Execute FlexUnit tests and publish reports -->
        <flexunit 
            workingDir="${bin.loc}"
            toDir="${report.loc}" 
            haltonfailure="false" 
            verbose="true" 
            localTrusted="true" >

          <additionalCompilerOption option="-define+=MY_CONST::foo,'BAR'" />
          
       </flexunit>
{code}

  was:
The FlexUnit Ant task does not support compiler options, yet there are some custom forks online
of FlexUnit which have added this support too 4.1.x.  Instead of people having to hunt down
those fork there should be a 4.1.x release which has this support.  This feature should ideally
added to 4.2.x if its does not 'break' any existing functionality.  GradleFX both supports
a 'additionalCompilerOptions' flag, but most FlexUnit tags are singular.  'additionalCompilerOption'
seems like a good match.

Example XML:

        <!-- Execute FlexUnit tests and publish reports -->
        <flexunit 
            workingDir="${bin.loc}"
            toDir="${report.loc}" 
            haltonfailure="false" 
            verbose="true" 
            localTrusted="true" >

          <additionalCompilerOption option="-define+=MY_CONST::foo,'BAR'" />
          
       </flexunit>



> As a User, I would like FlexUnit 4.1.0 to support compiler options so I can easily compile
more complicated Flash/Flex projects.
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-35090
>                 URL: https://issues.apache.org/jira/browse/FLEX-35090
>             Project: Apache Flex
>          Issue Type: New Feature
>          Components: FlexUnit
>    Affects Versions: FlexUnit 4.1
>            Reporter: Hays Clark
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The FlexUnit Ant task does not support compiler options, yet there are some custom forks
online of FlexUnit which have added this support too 4.1.x.  Instead of people having to hunt
down those fork there should be a 4.1.x release which has this support.  This feature should
ideally added to 4.2.x if its does not 'break' any existing functionality.  GradleFX both
supports a 'additionalCompilerOptions' flag, but most FlexUnit tags are singular.  'additionalCompilerOption'
seems like a good match.
> Example XML:
> {code:title=Example.xml}
>         <!-- Execute FlexUnit tests and publish reports -->
>         <flexunit 
>             workingDir="${bin.loc}"
>             toDir="${report.loc}" 
>             haltonfailure="false" 
>             verbose="true" 
>             localTrusted="true" >
>           <additionalCompilerOption option="-define+=MY_CONST::foo,'BAR'" />
>           
>        </flexunit>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message