"anil.saldhana(a)jboss.com" wrote : Why not have a plugin that works all the way from Beta4 to GA? The EJB3 Plugin has to account for the diffs in what AS *has* and what AS *needs* for an updated EJB3 Installation. So to make a single Plugin that smart enough to match these diffs is an investment of effort==time==money and we need to make sure we can justify those expenses. "adrian(a)jboss.org" wrote : Why waste time on Beta4? Its gone. Once the GA is out nobody will use Beta4. So here Adrian makes an argument that it's not worth it for Beta4. I happen to agree. However, we still have the standing question creeping up post GA - how will the Plugin releases work? It'd be great to have only one Plugin version per EJB3 release, and let it intelligently patch any AS after a certain cutoff (say, CR1). This way I can also tie the EJB3 Plugin into one of my Maven Plugins for AS Installation and make upgrades to the user completely transparent. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134992#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...