Efficient Add-on Development Without Frequent Publishing

I’m currently migrating my project to a modular structure using Jmix add-ons (Jmix 1.7.1 ). However, it’s very inefficient to make small changes in an add-on module, publish it, and then update the dependency in the main project every time for testing.

Is there a better way to develop and test add-ons without repeatedly publishing them? Ideally, I’d like to:

  • Edit add-ons locally and see changes reflected immediately in the main project.
  • Avoid the publish → update → test cycle for faster iteration.

What’s the recommended approach in Jmix for this workflow? Are there any best practices or sample projects demonstrating this?

The recommended approach is to use the Composite Projects feature. It solves exactly the problem that you described.

Regards,
Konstantin

1 Like