Support module nesting and improve backward compatibility for newer IDE versions#30
Support module nesting and improve backward compatibility for newer IDE versions#30arecmetafora wants to merge 2 commits into
Conversation
1804c30 to
b010dbf
Compare
|
@savvisingh merge is blocked because I cannot merge to a locked branch. Can you help me with merging this and publishing a new release of the plugin? Currently the plugin is no longer functional for the last 4 or 5 releases due to incompatibilities. I believe some maintainer has to create a feature branch so I can merge this into? |
@arecmetafora Let wait for @thsaravana he is the owner of this plugin But he is OOO, I don't know why there is this rule |
|
Closing stale PR. If this is a mistake, please re-open. |
|
This is not a stale PR. @savvisingh @thsaravana could you please take a look at it? Unfortunately this is a blocker for our whole company (100+ devs), currently we are using custom builds to work around it. Many thanks in advance and happy new year! |
Current Gradle settings limit the number of versions supported (
pluginUntilBuild), forcing a new plugin version for every single IDE version that is released. This is not necessary, instead we can usepluginSinceBuildto set the minimum supported version and no compatibility breaks will ever be introduced unless IntelliJ breaks compatibility.Additionally, a second commit introduces a fix for the support of nested modules, mentioned on issue #14 and already pushed before by closed in PR #15