Conversation
|
IMO: multi lib updates (of mostly unrelated libraries) should be split into individual commits, one per updated lib wrapper. Each commit should also get a proper commit message. "upgrade platform lib" for so many libraries is not sufficient to tell the story what the commit actually includes. This could be still fixed here since wrapper updates are usually folder based. e.g |
62d7d2f to
a9cdd73
Compare
|
@mbien done, |
|
As some check where in red I look a bit the log. looks like compiler.flags entries in the test generated lots of warning Maybe continuing the ordering of some items could reduce the |
matthiasblaesing
left a comment
There was a problem hiding this comment.
Looks sane to me.
upgrade libraries in platform cluster.
commons (io,lang3,logging,codec)
jsvg
upgrade the test framework update testNG 7.12.0 and junit (only to 5.14.4 not major but looks more easy thant 4 to 5 migration).
maven project generation use same version now
ant projet testng lib synchronized with 7.12.0
may help fixing: #9561 integrated the modification suggested by @matthiasblaesing
Used a new bundle to progress indicator as there is a bundle error, not sure the root cause java/testng/src/org/netbeans/modules/testng/ProgressIndicator.java