flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik de Bruin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34224) An option to specifiy the output folder is missing
Date Tue, 15 Apr 2014 12:19:26 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969477#comment-13969477

Erik de Bruin commented on FLEX-34224:

The way I implemented had the least impact on existing code paths. That made sense to me,
given that we're already in the the release cycle.

Is there a specific use case where the "bin" part would be a show stopper for the 0.0.1 release
and it's integration in FDT?

> An option to specifiy the output folder is missing
> --------------------------------------------------
>                 Key: FLEX-34224
>                 URL: https://issues.apache.org/jira/browse/FLEX-34224
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: FlexJS
>    Affects Versions: Apache FlexJS 1.0
>         Environment: All
>            Reporter: Stephanie Swiderski
>            Assignee: Erik de Bruin
>             Fix For: Apache FalconJx 1.0
> The current output folder is always "sourceFolder/package/../bin" 
> if "sourceFolder/package/main.mxml" is the entry point of the application.
> Usually ActionScript developers put their main file inside a package named after the
group they work for (for example:. org.apache.flex)

This message was sent by Atlassian JIRA

View raw message