You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like in the switchover from v4.1 to v4.2 somebody changed the spotless formatter parameters. So running 'mvn spotless:apply' locally reformats all of the 138 local 'pom.xml' files. And since nobody has yet run the new 'mvn spotless:apply' on the pom.xml files on github main, this means that a correctly formatted PR will now include all of those 138 files in the diff versus OH main.
EDIT: I think it may be the other way round. The 138 'pom.xml' files on github were reformatted, to a layout that is incompatible with the output produced by running 'mvn spotless:apply' locally.
@andrewfg We always do that after an release, but it has to be done manually, unfortunately.
@holgerfriedrichmvn spotless:apply clean install -DwithResolver=true -T 1.5C is what I usually use. It applies spotless, does a full build with bundle resolving and in parallel with 1.5 threads per core.
It looks like in the switchover from v4.1 to v4.2 somebody changed the spotless formatter parameters. So running 'mvn spotless:apply' locally reformats all of the 138 local 'pom.xml' files. And since nobody has yet run the new 'mvn spotless:apply' on the pom.xml files on github main, this means that a correctly formatted PR will now include all of those 138 files in the diff versus OH main.
EDIT: I think it may be the other way round. The 138 'pom.xml' files on github were reformatted, to a layout that is incompatible with the output produced by running 'mvn spotless:apply' locally.
Signed-off-by: Andrew Fiddian-Green software@whitebear.ch
The text was updated successfully, but these errors were encountered: