I'm pretty sure that there are people and customers that are still running on 1.4.2. maybe not much. but those will be screwed if they simply want to upgrade from jPDL 3.2.GA to 3.2.1. This would backfire if we upgrade JDK requirements or JBoss version between micro releases. For 3.3, it's a whole other discussion. that is where I'm very open to discuss this. Similar for jboss versions. Currently we build with 4.0.4.GA. I don't mind switching to 4.0.5. But i would mind switching to 4.2.0. I'm talking about the suite distribution here. What we can do is add more packages in the deploy directory. There we can put packages that you can deploy in other environments then the one we selected for the out-of-the-box experience. Also I think it's good if the project can handle many versions. But we already had a hard time setting up the simple integration test build. I think it would be a lot of effort to upgrade that integration test build for the matrix of jdk's and jbosses. Our current team would not be able to handle the extra load resulting from that. We need to focus on 1 set of dependencies. If we can handle variations, the better. But I don't want the team to be too much distracted from the resulting complexity of such a matrix. We better focus first on getting the integration tests running on multiple databases. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054211#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...