Debug Modules and Developer Console

[aderosso]

Is there a way of keeping the debug modules and the developer console out of a production build?

I was looking through the compiled output of our application and was wondering if there was a way to reduce the amount of unnecessary files for a production build.

[Blama]

Hi aderosso,

I just include files I don't want in my .war I deploy:

            <exclude name="WEB-INF/**/*.*" />
            <!-- Excluding generated SmartGWT debug files -->
            <exclude name="**/modules-debug/**" />
            <!-- Excluding generated SmartGWT precompressed files -->
            <exclude name="**/sc/modules/*.js.gz" />
            <exclude name="**/sc/system/development/*.js.gz" />
            <!-- Excluding generated SmartGWT skins -->
            <exclude name="**/sc/skins/EnterpriseBlue/**" />
            <exclude name="**/sc/skins/Graphite/**" />
            <exclude name="**/sc/skins/Simplicity/**" />
            <exclude name="**/sc/skins/Tahoe/fonts/**" />
            <exclude name="**/sc/skins/ToolSkin/**" />
            <exclude name="**/sc/skins/ToolSkinNative/**" />
            <!-- Excluding generated development files, currently breaks Development Console
            <exclude name="**/sc/system/development/**" />
            -->
            <!-- Excluding generated tools files -->
            <exclude name="**/tools/selenium/**" />
            <exclude name="**/tools/visualBuilder/**" />

Best regards
Blama

[Isomorphic]

We do not recommend removing the Developer Console because it is an extremely useful tool for troubleshooting live sites. We use it that way all the time.

Further, if you report a problem in a live deployment to Support, we will tell you to gather info using the Developer Console, and if you don't have it, then to deploy it first (it's just indispensable).