3 ms·
Back in the day , used to have all common dependency jars in server/lib folder and only deploy slim application war to the server . Reminds me of this
by devsatish 10y ago
Back in the day , used to have all common dependency jars in server/lib folder and only deploy slim application war to the server . Reminds me of this
- sytringy05 10y agoand remember how bad it was trying to get application server X to deploy your war file from a command line without exploding for some bizarre reason? It still actually makes me sad to think of the hours of my life wasted writing WLST jython scripts trying to get WebLogic to behave properly.
- HiJon89 10y agoWhat was the process for adding or removing a dependency? Changing a version? If two apps needed different versions?
- niftich 10y agoYou added the dependency to server/lib. You standardized on versions, and applied only security fixes, testing them in a separate environment first. You only upgraded versions of libs if you had a critical feature you couldn't live without, of if your existing libs were about to be deprecated and out-of-support. I'm not saying it wasn't a dark time, but it had its merits and drawbacks just like everything else.