Skip to content


Repository files navigation


Supports Right-click on project, Maven > Update project...

The connector will synchronize the project settings in a pom first fashion:

  • Adds Flash, Flex, Air nature to project,
  • Adds source, test, and resources paths to project source paths,
  • Adds Flex framework version to project (will generates "Flex 4.9.0" for flex-framework:,
  • Adds other SWC dependencies from local .m2 repository to project library paths.
  • Compiles locales under the src/main/locales/{locale} folder by default, support pom.xml overriding.

Contribute to the project

Contributing to the project necessitate some configuration, follow the steps bellow to successfully set-up your environment.

  1. Create the Flash Builder 4.x target platform as a p2 repository.

    The Features and Bundles Publisher Application (org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher) is a headless application that is capable of generating metadata (p2 repositories) from pre-build Eclipse bundles and features.

    In eclipse, create a new configuration: Run > Run Configurations... Select Eclipse Application. In the fieldset "Program to Run" select "Run an application" and choose org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher. In the Arguments tab, put the following in the text area "Program arguments":

    -metadataRepository file:<some location>\repository
    -artifactRepository file:<some location>\repository
    -source <location with a plugin and feature directory>;
    -configs win32.win32.x86_64

    In this example, the plugins in /<location with a plugin and feature directory>/plugins and features in /<location with a plugin and feature directory>/features will be published in the file:/<some location>/repository repository. The artifacts will also be published, and the repositories (artifacts.xml and content.xml) compressed. Run the configuration and repeat this step for each Flash Builder installation you have: 4.0, 4.5, 4.6 and 4.7. This will create different target platform.

    Note: you can have more information on creating a p2 repository in

  2. Clean and install the dependencies.

    If you have not already fetched the git submodule required (m2e-core), run the following command in the project root:

    git submodule update

    This will pull the tag 1.2.0 of the m2e-core repository in your project, it is required as m2e-flexmojos is built against this version.

    You need to install the provided maven module m2e-flexmojos-runtime, this maven module contains the runtime dependencies required by the connector. Install the maven artifact in your local repository by running:

    mvn -f m2e-flexmojos-runtime/pom.xml clean install

  3. Compile the project.

    Add the repository you created in your .m2/settings.xml in a profile as follow:

            <url>file:/<some location>\repository</url>
            <url>file:/<some location>\repository</url>

    Do not forget to use this profile when invoking maven on the project! It will allows Tycho to use the Flash Builder 4.x platform when building the m2e connector plugin. Note that you will also need to set-up a new Target Definition in eclipse to use the plugins and features of your Flash Builder installation.

    Run mvn clean install on the project root. You can also use the script once you declared the p2 repository in your maven user's settings.xml.

  4. Run and Debug from eclipse.

    Creates the Flash Builder 4.x target by opening preferences in Window > Preferences. In Plug-in Development > Target Platform, click on Add...

    Initialize the target definition with Nothing: Start with an empty target definition. Click on Next >.

    In the Locations tab, click on Add... and select your eclipse Flash Builder directory (the directory must contain a plugins and features directory).

    In the Environment tab, check that the Execution Environment is set to a JavaSE-1.6 compatible JRE.

    In the Arguments tab, add the following in the VM arguments text area: -Xms512m -Xmx1024m -XX:MaxPermSize=256m -XX:PermSize=64m

    Call this target platform Flash Builder 4.x, and make sure it is the only platform activated.

    When you launch the plug-in in run or debug mode, it will create an Eclipse Application in your Run/Debug Configuration. Open it and navigates to the Plug-ins tab, in the Launch with: drop-down, choose plugin-ins selected bellow only. Make sure all plug-ins under Target Platform are thick, and check that m2e plugins under Workspace are un-thick, this can cause compatibility problems.


The project uses a Bridge pattern which decouple the ProjectConfigurator from its MavenFlexPlugin. This pattern is used to cover the product and version space of different version of Flash Builder (4.0, 4.5, 4.6 and 4.7) but also different version of Maven Flex Plugin (Flexmojos 4.x, 5.x, 6.x and 7.x, and MavenFlexPlugin 1.0).

The bridge pattern is useful when both the class defining the implementation for different product and what it does vary often. The class itself can be thought of as the implementation and what the class do as the abstraction. It can also be thought of as two layers of abstraction. This pattern is often confused with the adapter pattern. In fact, the bridge pattern is implemented using the class adapter pattern, e.g. the Flexmojos7Adapter.

To wire this configuration of classes, the project is using Dependency Injection through and JSR specification. When a Right Click > Update Project configuration is requested, the class responsible for configuring the container select a compatible adapter plugin for FlexMavenPlugin from the pom artifacts. The configuration of the refined class for project configurator is selected at eclipse plugin load time.


Flexmojos m2e connector for Flash Builder 4.7. The connector supports pom.xml to project settings configuration (through Maven > Update project configuration in eclipse)






No releases published


No packages published