Sorry to hear that.
So far the rebel.xml generating should work correctly with “separate module per source set” option disabled, with the rebel.xml pointing to submodule/build/resources and submodule/build/classes. Perhaps your project defines the modules differently somehow or they’re actually source sets?
To be entirely certain we manage to fix it correctly, would it be possible to create a sample project which displays the same behavior?
However we’ll see if we can fix the behavior also when “separate module per source set” is enabled. Currently it indeed generates incorrect paths with classes/production/modulename or similar.
-
This reply was modified 9 hours, 21 minutes ago by
Meelis.
