Closed mbechto closed 1 week ago
Can confirm that we're also seeing this same behaviour on attempted deployment since upgrading to 3.1.14. Downgrading back to 3.1.13 solves the issue.
However, we are NOT explicitly excluding spring-devtools from our build as the initial report is.
Hmm, I wonder if making spring-devtools an optional dependency would help.
@tschuehly do you know what would be the spring recommended way to fix this?
Hmm, I wonder if making spring-devtools an optional dependency would help.
@tschuehly do you know what would be the spring recommended way to fix this?
I'm not sure. Maybe @mhalbritter can tell us?
Devtools should not be a required dependency of JTE.
If you need devtools to develop something, you should use optional=true
, like documented here.
If you depend on devtools for some functionality, i'd also use optional=true and then do a runtime class check to see if it's there.
I saw #398 included devtools for the FileWatcher
- that's not a good idea to include devtools just for the filewatcher. You could either use the java.nio
filewatcher or implement your own.
Thank you for looking in to it.
Since this causes problems to users in production, I've reverted the changes in #398 and published a new bugfix release.
@tschuehly we can reintroduce #398, once we have a proper solution for it.
Hi,
we just upgraded from 3.1.13 to 3.1.14 and got this on deployment:
Probably it stems from spring-devtools being excluded in our build. It was added as a dependency in #398. I guess this is normal behavior since one doesn't usually want to include devtools in a production build.