Home > Back-end >  Two projects rely on the same jars to integrate different versions
Two projects rely on the same jars to integrate different versions

Time:11-03

For example, a project I use spring4.0 package, there is a kind of be, for the project to another project with spring4.01 inside a class, these two classes respectively belong to their respective version, is not a version with them, get rid of any not, if put together at the same time will be submitted to the conflict, how to solve this problem

CodePudding user response:

Looking for high version supports corresponding method, high version removed is sure to provide the corresponding solution

CodePudding user response:

You first determine whether high version is compatible with low version of the function, high version have to delete or modify of low version, what is the effect of high version of the changes of low version, if there is no effect, can discard low version, with high version to build the project

CodePudding user response:

High versions of low do change, low version inside a class, in high version does not exist, use low version of the class can't find the abnormal, high use low version of the same version of a low version also have no, can't find the same kind

CodePudding user response:

It is never too ugly, is hand draw this to load the class you need?

CodePudding user response:

Finally know thank you
  • Related