Eduardo Martins
Eduardo Martins
@tadamski please please? ^^
@tadamski thanks for your feedback, personally I see no interest in making this change till the warning is gone, after all this would be replacing one warning (that is already...
@tadamski does this means that WFLY 36 will no longer produce this warning?
@bstansberry here is the BOMs "rework" PoC, in this particular case we will deliver a single (and standalone) tools BOM
> This simplest way to review, except for small details like my previous comment, is to compare the new boms with what's produced by building main: > > EE --...
@bstansberry I will delay the update of #17989 till we have everything settled on this one, cause I will need to do any agreed changes there too
PR updated post release
@bstansberry added a second commit so you can review only the changes from your previous review. So now the PR includes 4 *-with-tools BOMs, one for each "server" BOM, and...
> Besides the comments below I still see some discrepancies vs the boms generated from main with respect to exclusions. Diffing org.wildfly.bom:wildfly-ee I see those. Now checking changes...
@bstansberry dep management diff fixed, the EE BOM was missing plugin config: ``` UNMANAGED true ``` I have moved that (from all other server BOMs) to /server/pom.xml since such config...