0 Replies Latest reply on Nov 13, 2013 3:34 AM by Kevin Sewell

    Creating and maintaining a 7.2.x branch of JBoss AS

    Kevin Sewell Newbie

      I am planning to deploy JBoss AS 7.2 into production. I would prefer to have zero candidate release dependencies deployed in production. Those being Hibernate 4.2.0.CR1 and HornetQ 2.3.0.CR1. Upgrading Hibernate is fairly trivial and can be done by deploying the updated jars into the modules directory.


      Upgrading HornetQ is another story. Between 2.3.0.CR1 and 2.3.0.Final the HornetQ developers made a couple of API breaking changes... which they are allowed to do. However, JBoss 7.2.0.Final is now tied to the API of 2.3.0.CR1, with HornetQ sitting on version 2.3.11.Final. Whilst I am happy to clone the repo and make the necessary changes outside of the Wildfly repo, I was wondering if we could create a 7.2.x branch where developers can contribute to.