IntelliJ IDEA Jmix plugin for migration

Hi,

I’m looking to start the migration from CUBA to Jmix. I’m developing using the CUBA plugin for IntelliJ IDEA. Are there any problems or conflicts to be aware of if I install the Jmix plugin simultaneously?

*** DUPLICATED from CUBA forum

Hi,

you can have both CUBA and Jmix plugin installed on the same IntelliJ installation instance, but per default you will not be able to start both projects at the same time, because they can’t share the same port on the in-built local development webserver.
If your Jmix uses Java 17, and CUBA uses 11, that may be the problem too, on the same system.
CUBA plugin is certified to work up to a certain version of IntelliJ IDEA, if you have a version newer than that, CUBA plugin will not work.
While there are ways to set this right, I was OK with that because I decided to not use the CUBA to Jmix project converter, and to start from scratch, so I can experience Jmix2 that way. Defined the entities and views again from zero, and copy-pasted the code and then corrected it for Jmix2, copied the data later.
But you should give a chance to the project converter, if the project is simple enough and you have a lot of entities and views, it will save you time.
I’m also using this to have and manage various versions on IntelliJ JetBrains Toolbox App: Manage Your Tools with Ease
→ this saved me a lot of time, because there is always a day or 2 before the new version of Jmix plugin is released for the new version of IntelliJ IDEA. You can also set the version of IntelliJ IDEA that will start and open the project
If I would need to have both projects running simultaneously, I would use different VMs for each CUBA and Jmix2, to have a clean separation and a simple situation to solve potential problems.

Kind regards,
Mladen

2 Likes

Thanks for the detailed response Mladen. I am indeed using Java 11 with CUBA and my existing project is quite complex with my own libraries and several 3rd party dependencies.

I’m very tempted like you suggest to go for the VM solution for Jmix initially and test the waters regarding migration vs starting from scratch.