Move bundled libraries out of plugins

Move bundled libraries out of plugins
Committed: https://code.google.com/p/dart/source/detail?r=1857

[danrubel, 2011-11-22 12:40:08]

This is the first step in multi step process for bundling an SDK with Dart
Editor...

* Moved bundled libraries out of plugins into a "libraries" directory
* Modified the library manager to read bundled libraries from new "libraries"
directory
* Modified build to create this new "libraries" directory
* Removed references to old bundled library plugins
* Will delete the library plugin projects in future CL

This does not address per project library managers.
The libraries directory will undoubtedly change format when we add VM support,
and move into an SDK directory at some future date.

New setup step when developing Dart Editor.... see editor/docs/README.txt

[devoncarew, 2011-11-22 18:50:19]

lgtm

Fantastic stuff! This will resolve several user issues and put us closer towards
consuming a SDK.

A few things:

The server launch CL I just landed has changes in many of the same files. You
should do an update and merge to make sure that things still look good.

I'm concerned about the new ant step for editor developers - we'll have to run
this (and remember to run it ) fairly frequently. Per our discussion, I like a
linking based approach. We should also print out where we copy / link the
libraries directory, so we give the developer a chance to modify it as
necessary.

The coping step that modifies the dart file names is problematic because then
dart developers working on the core libs will not be able to use the editor to
do their work.

[Mark R Russell, 2011-11-23 13:41:15]

LGTM on the build stuff

[danrubel, 2011-11-27 16:07:13]

On 2011/11/22 18:50:19, devoncarew wrote:
> The server launch CL I just landed has changes in many of the same files. You
> should do an update and merge to make sure that things still look good.

Thanks for the heads up. Changes merged.

> I'm concerned about the new ant step for editor developers - we'll have to run
> this (and remember to run it ) fairly frequently. Per our discussion, I like a
> linking based approach. We should also print out where we copy / link the
> libraries directory, so we give the developer a chance to modify it as
> necessary.

The script prints a message indicating the location of the "libraries"
directory.
I also updated the error message indicating what Ant properties need to be
defined.

> The coping step that modifies the dart file names is problematic because then
> dart developers working on the core libs will not be able to use the editor to
> do their work.

Good point. I've split that change out into a separate CL that renames the
source file rather than renaming the files when building the "libraries"
directory.