flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLEX-34318) [Mavenizer] Refactor the Mavenizer in preparation of future mavenized releases of flex
Date Fri, 05 Sep 2014 13:20:28 GMT

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

Christofer Dutz resolved FLEX-34318.
       Resolution: Fixed
    Fix Version/s: Mavenizer 1.0

Implemented the changes needed to split up Apache Flex and Adobe artifacts.

> [Mavenizer] Refactor the Mavenizer in preparation of future mavenized releases of flex
> --------------------------------------------------------------------------------------
>                 Key: FLEX-34318
>                 URL: https://issues.apache.org/jira/browse/FLEX-34318
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Utils: Mavenizer
>            Reporter: Christofer Dutz
>            Assignee: Christofer Dutz
>             Fix For: Mavenizer 1.0
> The current version of the Mavenizer produces output in which Apache and Adobe artifacts
are mixed. This makes it hard for us to publish Flex as Maven artifacts. In order to be able
to publish Flex in the future the following changes have to be performed:
> - The Apache Artifacts should no longer directly reference Adobe artifacts (Playerglobal,
> - For each Air and Flash version a dummy artifact should be generated org.apache.flex.runtime:flashplayer:version:pom
or org.apache.flex.runtime:air:version:pom
> - The Mavenizer logic should be cleaned up dramatically.
> - The Mavenizer logic should be split up into Air, Flash and Flex mavenizers.
> - The Mavenizer should be split up into reuseable modules so we can use the Air and the
Flash Mavenizer from other projects such as Flexmojos.

This message was sent by Atlassian JIRA

View raw message