Closed jukzi closed 1 month ago
This pull request changes some projects for the first time in this development cycle. Therefore the following files need a version increment:
org.eclipse.jdt.annotation/META-INF/MANIFEST.MF
org.eclipse.jdt.annotation/pom.xml
org.eclipse.jdt.apt.tests/META-INF/MANIFEST.MF
org.eclipse.jdt.apt.tests/pom.xml
org.eclipse.jdt.compiler.apt.tests/META-INF/MANIFEST.MF
org.eclipse.jdt.compiler.apt.tests/pom.xml
org.eclipse.jdt.core.tests.builder.mockcompiler/META-INF/MANIFEST.MF
org.eclipse.jdt.core.tests.builder.mockcompiler/pom.xml
An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.
Further information are available in Common Build Issues - Missing version increments.
ignoring random fails and merging before likely mergeconflicts happen
I beg your pardon, you are changing 1650 files, request a review and can't hold your horses waiting for the review? Do you expect a voluntary committer to react to your request on the same day, perhaps same hour, no matter what his job might require from him?
What makes you so sure that there is absolutely no problem in this commit?
I'm sure there are better ways to minimize merge conflicts.
Please also coordinate with @jarthana wrt BETA_JAVA24, since you actually missed the window where we had only one active branch.
The BETA branch hasn't yet evolved, but I do have changes in my PR. So, I guess that'll have to deal with the merge conflicts. :( Let's see how that goes.
enabled organize imports and automated cleanup
https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2579