Opened 14 years ago
Closed 13 years ago
#1706 closed defect (fixed)
allow buildin xdomain resources for external modules
| Reported by: | James Burke | Owned by: | James Burke |
|---|---|---|---|
| Priority: | high | Milestone: | 0.9 |
| Component: | BuildSystem | Version: | 0.3 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Modules whose resources are outside of the dojo tree don't get .xd.js files generated for them. Need to look at the depedencies.prefixes entries in the profile build file to process external resources.
Change History (5)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
(In [6389]) References #1706: now external module resources get .xd.js files, but no string-interning yet. Fix for xd builds that do not have flattened resources. Also, converted xdgen process to javascript instead of java, to make other xd bugs easier to fix. All your base are belong to javascript.
comment:3 Changed 14 years ago by
| Milestone: | 0.4.1 → 0.5 |
|---|
Moving to 0.5. Want to pick this up for 0.4.1, but I don't think it is a blocker. The main Dojo tree can be xdomain built. If external modules want xdomain building to work, they can always choose to download the latest build tools.
comment:4 Changed 14 years ago by
| Component: | General → BuildSystem |
|---|
More info: if you put a dependencies.prefixes array in your build profile, currently the build process does not look at those resource directories to generate xdomain files, when it really should. Right now, .xd.js files (the xd resource files) are only generated for things under src/.