Import Flexmojos Projects to IntelliJ IDEA 9
Note: before starting please make sure that Maven Integration Extension plugin is enabled at Settings (Ctrl+Alt+S), Plugins page.
If you are using Flexmojos version 3.4 or higher, then the only thing you need to do to import your Flexmojos project to IntelliJ IDEA is to click New Project on the File menu and select your pom.xml file.
That’s all! Right after that you have full coding assistance, ability to compile your project in the same way as Maven does, and to run and debug your application in IntelliJ IDEA.
Note: get more information about configuring Flex SDK sources and documentation for Flexmojos projects.
How does this work? When importing Flexmojos project, IntelliJ IDEA:
- Creates special type of SDK — Flexmojos SDK with name compiler-XXX.pom that contains information required to launch Flex compiler and debugger. In SDK configuration dialog you may increase Flex compiler heap (if your project is huge) and configure AIR paths (if you want to run/debug AIR applications):
- Creates modules with Flex facets.
- Generates compiler configuration file for each facet (target/XXX-config-report.xml). This feature is new in Flexmojos 3.4; instructions for previous Flexmojos versions project are below. IntelliJ IDEA uses these files as custom compiler configuration for Flex compilation:
If something goes wrong and you have red code in editor or you have problems with compiling project or launching tests in IDEA then you should make sure that Flex compiler configuration files (target/XXX-config-report.xml) and some other auxiliary files (target/classes/config-XXX) are up-to-date. To do that please run following from command line for your root project:
mvn compile -DconfigurationReport=true
Note that it is important to use compile because in this case dependencies between projects will be resolved as files from target folders whereas install will generate references to local maven repository that is incorrect for development purpose.
-DconfigurationReport=true flag means the same as <configurationReport>true<configurationReport> option in pom.xml but using command line flag is better because you need to skip configuration report generation when executing install goal.
Subscribe to Blog updates
Thanks, we've got you!
Import Postman Collections to the HTTP Client
We know that many of you use Postman collections and want to stay in the flow while working with them. This means staying inside IntelliJ IDEA and not switching to a different app. Great news! You can now effortlessly transform Postman collections into .http and use them in the HTTP Client …
What’s New in IntelliJ IDEA 2023.1 for Spring Developers
The IntelliJ IDEA 2023.1 release came packed with updates for Spring. This blog post will highlight the most noticeable changes, including full support for Lombok, a reworked Spring tool window, navigation for Spring Security rules, Spring Security 6 support, and more. Remember that these featur…
‘Quick’ Features in IntelliJ IDEA
A few IntelliJ IDEA features or actions include the term ‘quick’. Do they speed up certain processes? Let’s find out. In this blog post, I’ll cover what these features are, why you need them, and how you can use them. 1. Quick Lists If you have actions that you use regularly but don’t have shortcut…
5 Best Features for Profiling Java Code In IntelliJ IDEA
When it comes to apps functioning efficiently, there is always room for improvement. Fast, lag-free, smooth operation – what else can a Java developer dream of? However, when you aim for this level of perfection in your app, you will need a comprehensive toolset to monitor performance and identif…