Build application's source files without building dojo source everytime.

[virsir]

I think there is a common usage of dojo build system that is to build the dojo source and the application source in separate layer files.

In development, the dojo source remains stable(and the application dependencies on dojo will be stable at some time), but the application's js files change everyday. So it should be better if the dojo build system can just build the application's files and use the built dojo lib before, because it can save lots of time and make the development process more agile.

[James Burke]

This is complicated by the transforms done to built files. Probably will not get to it until Dojo 2.0.

[bill]

not sure if these tickets are even valid anymore but assigning to rawld to check

[ben hockey]

Rawld don't you have a ticket you opened recently for this same feature in the new builder? Should we close this as a duplicate?

[Colin Snover]

1.8 is frozen. Move all enhancements to next release. If you need an exemption from the freeze for this ticket, contact me immediately.

[bill]

I'd suggest wontfix, because the builds run pretty quickly nowadays anyway, assuming copyTests=false.

[dylan]

Duplicate of #13214.
Duplicate of #13214 (favoring the newer ticket as it has a bit more detail on the approach).

The main benefit of this change is not about a build taking too long to build, but rather for organizations that share a common layer of built files, and then just want to build their code that leverages that layer.