Community
Participate
Working Groups
Write commands that run during the build to create the combined Dojo projects mentioned in bug 352820 - Combine dojo runtime project and widget project. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=352820 Here's a note from Will Smythe with details and justification for the change: In RBD and CE we separated the Dojo widgets (EGL source + .js external types) from the Dojo runtime. So, after creating a RUI project, the developer would have the following projects in their workspace: * EGL RUI widgets * EGL Dojo widgets * Dojo runtime (local) * New project Besides the complexity of multiple Dojo projects, the new project's build path references the Dojo runtime project (not the Dojo widgets project) - this is confusing to someone that doesn't understand the intricacies of our project dependency structure. Although we don't expose this complexity during project creation, the developer is exposed to it whenever they change the build path or need to switch from local to remote. The proposal is to combine the Dojo widgets and Dojo runtime into a single project. This makes the project dependencies much simpler, which also makes importing/exporting/sharing projects simpler. There is also a proposal to reduce the number of Dojo runtime options (from 3 to 2). So, the net is that we go from this set of total Dojo-related projects: * EGL Dojo widgets * Dojo (local) * Dojo (Google) * Dojo (AOL) to this: * EGL Dojo widgets + runtime (local) * EGL Dojo widgets + uruntime (remote/Google) .. resulting in a workspace (using the scenario above) that looks like this: * EGL RUI widgets * EGL Dojo widgets + runtime (local) * New project Less projects and less project dependency complexity. One less runtime project (AOL) to test against. Although our target audience will be more advanced, if there are places where we can relatively easily simplify things, we should. This is one area that has bothered me for awhile because I have seen this trip up and confuse lots of people ...
*** This bug has been marked as a duplicate of bug 356423 ***