There are many reasons for the parent problem on the Internet. What is the built-in version is too low to check? In fact, it is still a problem of maven (gradle) dependency. After all, springboot is still a Maven project. When there is a problem with environmental dependencies, you can look for it compared to normal Maven dependencies.
If you want to import your own version, there is no problem. Make sure that the maven project is matched with the warehouse, and your network speed is no problem. You can delete the corresponding thing in the repository and let it re-import.
This is no problem, but I installed two IDEAs in hand, and the project opened and opened. Somehow, it had a little impact. I re-selected the Maven settings file in IDEA, and it was automatically good.
(Inexplicably, the configuration display is the same, and it took a long time)
Purely off-topic, just look at the problem above.
Java's dependency package problem is really disgusting! ! ! !
Although I know this is mainly related to my lack of understanding of technology, it is difficult for novices to rule out the existence of the structure of the error, which is really not reasonable. When the graduate student just entered the school, the teacher asked the SSM to help his brother to get started, but he was stuck in the environment configuration. Often due to the difference in network speed or machine configuration, it will be difficult to reproduce and be stuck by various problems. These issues have nothing to do with the code itself, including the basic principles you need to understand to use the architecture. In the end, as stupid as I was, he was finally blocked from the door, did nothing to help, spent a lot of time returning to Alexander, and the teacher was naturally very upset. . .
In this competition, the big data installation environment also has a lot of pits, but fortunately, most of them have basic rules to follow. As long as it is a structural problem, it can be investigated. I was bothered by the fact that the jar package for setting up the test environment was defective, and it took me a week to find it. . .
The most disgusting thing when Java ’s mainstream framework started is that he is a bunch of packages. Whichever problem occurs may affect the whole. Of course, whether you are online speed, cache or version, warehouse, maven configuration, None of them are independent and excluded. For example, the most common is that the network speed is not good, and there will be an incomplete cache. The prompt message only tells you that there is a problem with this package and the performance will be affected. However, if you cannot find the root cause, there is no way to completely solve this problem. Even if the root cause is solved by you, the caching and configuration caused by your previous wrong operation will become a new problem.
The veteran will naturally have his own set of investigation mechanism based on experience, but the novice is not even skilled in the structure, and naturally will be dizzy.
Springboot can solve the problem to a certain extent by using a series of methods that are greater than the configuration, but the granularity of the positioning and troubleshooting is still not detailed enough. You should track the download status, cache status, dependency status, conflict status, etc. Verify the file.
Nonsense, actively get sprayed! It was mainly disgusted by these errors that had nothing to do with the logic of the code and could not be clearly located. I complained two words to vent my grievances.
