Hi @kares ! thanks for checking :-D
I've updated the lib/pom.rb to reflect the xml version.
If I run run ./mvnw package on my local machine, it also updates lib/pom.xml and core/pom.xml just inverting of position the mvn's groupid, for example:

diff --git a/lib/pom.xml b/lib/pom.xml
index 63786be945..035ba65cbc 100644
--- a/lib/pom.xml
+++ b/lib/pom.xml
@@ -39,8 +39,8 @@ DO NOT MODIFY - GENERATED CODE
       <scope>provided</scope>
       <exclusions>
         <exclusion>
-          <groupId>rubygems</groupId>
           <artifactId>jar-dependencies</artifactId>
+          <groupId>rubygems</groupId>
         </exclusion>
       </exclusions>
     </dependency>

Is it correct? Or after the mvn package should I commit also the changed lines by maven?

@andsel At some point maven changed something and ordering of processing a Map changes the order (Ruby stuff is put into a Map and Java side walks it). A newer Maven will put it in the same order as we have it (we all made sure we were using newer maven at one point because we were playing ping pong with the generated xml files.

If it is not possible to update maven let me know and we will merge this as-is and I will correct that ordering manually as part of the merge

@enebo I would have avoided playing ping pong on the xmls. However with commit 1356098 I've updated the core/pom.xml and lib/pom.xml with the new version of irb as generated by the maven wrapper.
Let me know if keep the commit or remove, before merge.

I merged this manually to avoid the reordering commit, and it is on master as of 4a1e6fc.

Thanks for the help!