The Eclipse project changed to a MAVEN project, resulting in SVN's inability to compare historical data with the workaround

This problem did not find the right answer, and finally came up with a solution, in this record.

Problem description

When I reconstructed the old Eclipse project as a maven project, I created a new MAVEN project and then put the corresponding data in the corresponding location, and finally the MAVEN project was successful, but all the files in the MAVEN project were not managed when I reconnected to SVN. That is, there is no comparison with the SVN version of history.

Analysis

Comparing the original Eclipse project with the reconstructed MAVEN project directory results, we found that the SRC folder had two fewer folders, Main and Java, which could be different from the directory structure.

Solution:

1, manually modify the original Eclipse project structure on SVN, SRC under the creation of the main folder, the main folder to create a Java folder, the SRC under the package moved to the Java directory, the Resources folder under Main, modify the completion.

2. The MAVEN project re-connects the modified SVN resource.

3. You should be able to connect to SVN at this time and compare it to the historical version. Then you can submit the need to submit up, do not need to delete it.

The Eclipse project changed to a MAVEN project, resulting in SVN's inability to compare historical data with the workaround