Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Date: Tue, 13 Nov 2012 17:32:11 +0000 (UTC)
From: "Christofer Dutz (JIRA)" <jira@apache.org>
To: flex-dev@incubator.apache.org
Message-ID: <1166479820.108908.1352827931974.JavaMail.jiratomcat@arcas>
In-Reply-To: <456864035.108637.1352825532674.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (FLEX-33256) [Mavenizer] Change the code that
 the empty zip is generated at runtime so no binary artifacts have to be
 added to the repository.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christofer Dutz commented on FLEX-33256:
----------------------------------------

Done ... you can also delete the entire resources folder ... As I mentioned before the CSV file was a relict from earlier versions and now I am generating empty resource bundles with 2 lines of code ... so the binay version of the empty zip is also no longer needed.
                
> [Mavenizer] Change the code that the empty zip is generated at runtime so no binary artifacts have to be added to the repository.
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-33256
>                 URL: https://issues.apache.org/jira/browse/FLEX-33256
>             Project: Apache Flex
>          Issue Type: Improvement
>            Reporter: Christofer Dutz
>         Attachments: FLEX-33256.patch
>
>
> Currently the Mavenizer contains the binary of an empty zip, which is used as a dummy-resource file. As it's a stirict Apache policy no to add binary files to the repo, I would suggest to dynamically create that zip file in code and hereby avoid problems with binary resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira