Thanks for the input, we'll take it into consideration.
One more packaging problem. When we generate the catalog the final output is a jar file with the DDL, java classes and a catalog.txt file
This txt file is specific to an enviorment. Which means for QA i need a different STG and production i need a differet jar file.
The binaries in my opinion should be seperated from the enviorment specific configurations.
Hence the jar should be deployable till production with out any changes, just the txt file having all node related info should be generated seperately. This way we can seperate code from release activites/ deployment