custom widgets not being resolved

[gerhard presser]

my dojo.js resides at

/scripts/dojo/dojo.js

I have some custom widgets, which I load via

dojo.require("a.b.C")

till 1.6.1 the widget was loaded from

/scripts/a/b/C.js

but in 1.7.0b1

/scripts/dojo/a/b/C.js

is being loaded which results in an error 500

[Rawld Gill]

(In [25483]) added default build switch for profiles to make top-level modules siblings of dojo; fixes #13192

[Rawld Gill]

The has feature "config-tlmSiblingOfDojo" instructs the loader to assume top-level modules are sibling to dojo, just like in v1.6-. For example, given the module id "a.b.c", "a" is the top-level module. If you have

scripts/dojo/

then "a.b.c" would reside at

scripts/a/b/c.js

assiming "config-tlmSiblingOfDojo" it truthy.

The dev version defaults "config-tlmSiblingOfDojo" to 1. v1.7.0b1 did not include any default value for this switch with implies a value of false. That's why you saw the strange behavior.

Please reopen if you are seeing the above behavior in trunk or in beta1.

Thanks for the report!

[ebengtso]

I'm having the same problem on 1.7.0b1

The workaround is to register the module path

dojo.registerModulePath("a","../a");

[gerhard presser]

I think this issue will be fixed in 1.7.0b2. I'm trying to test it with current trunk

Replying to ebengtso:

I'm having the same problem on 1.7.0b1

The workaround is to register the module path

dojo.registerModulePath("a","../a");

[Rawld Gill]

Should have always worked in the src version; fixed in the release version in [25483]