Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353521 - Create combined Dojo projects during the build
Summary: Create combined Dojo projects during the build
Status: CLOSED DUPLICATE of bug 356423
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-01 15:43 EDT by Matt Heitz CLA
Modified: 2017-02-23 14:14 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Heitz CLA 2011-08-01 15:43:02 EDT
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 ...
Comment 1 Matt Heitz CLA 2011-09-01 09:37:02 EDT

*** This bug has been marked as a duplicate of bug 356423 ***