| FYI, some of this can be achieved once we re-organize modules, so that each tree of modules represents related modules that need to be built together. Then a set of mvn commands can build parts faster... for example, if all ActiveMQ related modules were in a top-level components/activemq module, then one might be able to: mvn -f components/activemq/pom.xml mvn -f assemblies/pom.xml If dependencies are organized correctly then, this should update all activemq related modules for the server. But to do more optimizations may be much more work, as it requires fixing all of the maven plugins, and maybe even some of maven to skip steps when they are deemed up to date. --jason On Nov 6, 2006, at 2:33 AM, Vamsavardhana Reddy wrote: Testing code changes in G was and still is a painfully long process. Testing changes to admin console is ok(?) to some extent. I use Eclipse for development. Some changes could be tested quickly while using remote debug, but, you can not be sure which ones and once the IDE complains "Hot code replacement failed" or you disconnect the debugger, the server needs to be built again. Sometimes a build will fail since Eclipse knocks-out xml-beans classes and at this stage the only option is to do a rebuild. We should also consider some improvements to the build process so that the module that is modified can be specified as a parameter to the build command and it will build only those modules/configs that need to be built for the changes to get reflected in the server. IMHO, any improvement in this aspect of G (to be able to test changes quickly) will have a dramatic improvement in the productivity of G Developers. |
