Hi, yes they should be kept in sync. If you are up for it, can you send PR to sync it?

-- tomaz On Thu, Aug 21, 2014 at 8:51 AM, Chao Wang <chaowan(a)redhat.com <mailto:chaowan@redhat.com>> wrote: Hi, I noticed that component versions are sometimes different (newer or older) between Wildfly and Wildfly-Core pom.xml, for instance, version.org.apache.httpcomponents.httpclient is 4.2.6 in Wildfly and 4.2.1 in Wildfly-Core /< <version.org.apache.httpcomponents.httpclient>4.2.6</version.org.apache.httpcomponents.httpclient>// //< <version.org.apache.httpcomponents.httpcore>4.2.5</version.org.apache.httpcomponents.httpcore>// //< <version.org.apache.james.apache-mime4j>0.6</version.org.apache.james.apache-mime4j>// //---// //> <version.org.apache.httpcomponents.httpclient>4.2.1</version.org.apache.httpcomponents.httpclient>// //54,62d10/ version.org.jboss.modules.jboss-modules is 1.3.3.Final in Wildfly and 1.3.4.Final in Wildfly-Core: /< <version.org.jboss.modules.jboss-modules>1.3.3.Final</version.org.jboss.modules.jboss-modules>// //---// //> <version.org.jboss.modules.jboss-modules>1.3.4.Final</version.org.jboss.modules.jboss-modules>// //113,114d31/ As the core is split from previous whole Wildfly, in this case, do they both need to be coherent in a shared component upgrade? Chao _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/wildfly-dev