[Dojo-interest] Custom namespace fails after build

[James Bennett]

I've been working on translating all of the existing JavaScript used
in Django to Dojo packages, and I've put them all into a custom
'django' namespace. When they're all in separate files, dynamically
loaded, all is well and everything works as expected. But when I put
together a profile that includes the Django packages and the needed
Dojo modules, one set of Django packages mysteriously stops working;
the only error I've been able to coax out of a browser is that it
can't load the modules.

The directory layout I'm building from looks like this:

django/
--admin.js
--admin/
----AutoPopulate.js
----CollapsedFieldsets.js
----RelatedLookups.js
--datetime.js
--datetime/
----calendar.js
--string.js
--util.js
--widget/
----DateTime.js
----SelectBox.js
----SelectFilter.js

Everything comes up fine except for the modules in the 'admin'
directory; Dojo errors out with 'Could not load
django.admin.CollapsedFieldsets' and, if references to it are removed
from the build, then the error states that django.admin.AutoPopulate
and django.admin.RelatedLookups cannot be loaded.

I've double-checked the __package__.js for the admin packages, and it
looks fine (and works fine when it's dynamically loading files via XHR
-- doing "dojo.require('django.admin.*')" loads them all and functions
which rely on them are fine).

Does anyone have any suggestions on where to turn next to try to track
down the source of the problem?

For reference purposes, here's a copy of the custom dojo.js that comes
out of Ant: http://files.shtuff.us/dojo.js


--
"May the forces of evil become confused on the way to your house."
  -- George Carlin