Build fails only for one of our dev.

[Ethorsen]

Sencha Cmd 3.0.2.288

Java v1.6.0_24 or v1.6.0_21

Command runned:
$ sencha app build testing

For all our dev team, the app compiles perfectly. But only for one of us, it gives errors as follow:

[INF] Processing source dependencies

[ERR] Failed to find file for @core

required by /[...]/touch/src/Evented.js

[ERR]

[ERR] BUILD FAILED

[ERR] com.sencha.exceptions.BasicException: The following error occurred while executing this line:

[ERR] /[...]/.sencha/app/build-impl.xml:137: com.sencha.exceptions.ExScript: Wrapped com.sencha.exceptions.BasicException: com.sencha.exceptions.ExBuild: Failed to find any files for @core (x-app-build#273)

[ERR] runAppBuild (x-app-build:273)

[ERR] [anonymous] (x-app-build:545)
[ERR] x_app_build (x-app-build:543)
[ERR] <script> (anonymous:1)
[ERR] at com.sencha.exceptions.BasicException.wrap(BasicException.java:43)

And theres a bunch of similar errors after that.

I know the problem has nothing to do with Sencha Cmd as it works for all of us. But does someone have an idea why it wouldn't work only for him? What system config could be different maybe with java or ant or .. ?


Thank you
Eric

[dongryphon]

It seems like the framework src files are not being found. The paths to the framework are somewhat indirect to allow multiple applications in a workspace to share a single copy of the files. I suspect the difference is that some of these files have been moved or deleted. Or possible one of the configuration files (.sencha/app/sencha.cfg and .sencha/workspace/sencha.cfg) is missing or modified.

[dongryphon]

Another, though less likely, possibility is that there is a local.properties file in the application root folder (next to build.xml).

The purpose of local.properties is to contain local machine settings that are not desired to be shared with other members of the team. For example, if you add custom build steps and need user names or credentials, these can be placed in local.properties and never added to source control.

The presence of local.properties is not required but if there is one, the build script will reads its properties very early so that they will take priority over other values.

[Ethorsen]

Thank you for the suggestions.

I did take a look at .sencha folder and as this is checked in GIT the files are exactly the same.

I will verify with him for the local.properties file. I would be surprised if there would be one in sencha root folder, but maybe there is one in PATH that would conflict.