Runtime gradle dependency issues

LabKey Support Forum (Inactive)
Runtime gradle dependency issues Susan Hert  2017-10-05 10:54
Status: Closed
 
Here's something you wouldn't normally want to do, and, given that the directories are identical, I don't have much hope that this will be result in anything different, but I wonder if you will get the same results if you swap in the 17.1 versions of the modules instead of the 17.2 versions. To do this, you would need to remove the following from the 17.2 deployment :
- build/deploy/modules/<first module>.module file
- build/deploy/modules/<first module> directory
- build/deploy/modules/<second module>.module file
- build/deploy/modules/<second module> directory

Then copy the <first module>.module and <second module>.module files from the 17.1 deployment into the build/deploy/modules directory. (When Tomcat restarts, it will explode each module to create their respective directories.)