@powellke -
Thanks! That is a +1 on that. We have an issue in the 3.0.x to 3.1 upgrade process that does not correct the workspace.build.dir property.
Another way to correct all of that is to generate a fresh workspace in 3.1 and copy the .sencha/workspace folder over the one in your 3.0.x-generated workspace.
In a Cmd 3.1-generated workspace, the .sencha/workspace/sencha.cfg looks like this:
Code:
#Fri, 15 Mar 2013 13:23:33 -0700
# -----------------------------------------------------------------------------
# This file contains configuration options that apply to all applications in
# the workspace. By convention, these options start with "workspace." but any
# option can be set here. Options specified in an application's sencha.cfg will
# take priority over those values contained in this file. These options will
# take priority over configuration values in Sencha Cmd or a framework plugin.
# -----------------------------------------------------------------------------
# This configuration property (if set) is included by default in all compile
# commands executed according to this formulation:
#
# sencha compile -classpath=...,${framework.classpath},${workspace.classpath},${app.classpath}
#workspace.classpath=
#------------------------------------------------------------------------------
# This is the folder for build outputs in the workspace
workspace.build.dir=${workspace.dir}/build
#------------------------------------------------------------------------------
# This folder contains all generated and extracted packages.
workspace.packages.dir=${workspace.dir}/packages
# =============================================================================
# Customizations go below this divider to avoid merge conflicts on upgrade
# =============================================================================
workspace.cmd.version=3.1.0.239
ext.dir=${workspace.dir}/ext