SystemLibraryManager normalized URI test

SystemLibraryManager config update 
Committed: https://code.google.com/p/dart/source/detail?r=6152

[zundel, 2012-04-03 14:32:37]

(see the diff I sent as a separate message)

https://chromiumcodereview.appspot.com/9950092/diff/1/editor/tools/plugins/co...
File
editor/tools/plugins/com.google.dart.tools.core_test/src/com/google/dart/tools/core/internal/model/SystemLibraryManagerProviderTest.java
(right):

https://chromiumcodereview.appspot.com/9950092/diff/1/editor/tools/plugins/co...
editor/tools/plugins/com.google.dart.tools.core_test/src/com/google/dart/tools/core/internal/model/SystemLibraryManagerProviderTest.java:99:
// TODO (danrubel) move this test into the analysis or import tests ?
I agree - it doesn't seem right to test here logic which isn't in the editor. 
If we change something that breaks this down in SystemLibraryManager we might
not see it.

I pushed these tests down to SystemLibraryManagerTest and got them to work.  One
trick is that with the new dart-sdk path, you have to tell JUnit where to find
the sdk.  I do this by adding this VM argument:

-Dcom.google.dart.sdk=/home/zundel/dart/out/Debug_ia32/dart-sdk

[danrubel, 2012-04-03 23:17:04]

https://chromiumcodereview.appspot.com/9950092/diff/1/editor/tools/plugins/co...
File
editor/tools/plugins/com.google.dart.tools.core_test/src/com/google/dart/tools/core/internal/model/SystemLibraryManagerProviderTest.java
(right):

https://chromiumcodereview.appspot.com/9950092/diff/1/editor/tools/plugins/co...
editor/tools/plugins/com.google.dart.tools.core_test/src/com/google/dart/tools/core/internal/model/SystemLibraryManagerProviderTest.java:99:
// TODO (danrubel) move this test into the analysis or import tests ?
On 2012/04/03 14:32:37, zundel wrote:
> I agree - it doesn't seem right to test here logic which isn't in the editor. 
> If we change something that breaks this down in SystemLibraryManager we might
> not see it.
> 
> I pushed these tests down to SystemLibraryManagerTest and got them to work. 
One
> trick is that with the new dart-sdk path, you have to tell JUnit where to find
> the sdk.  I do this by adding this VM argument:
> 
> -Dcom.google.dart.sdk=/home/zundel/dart/out/Debug_ia32/dart-sdk

Moved test into https://chromiumcodereview.appspot.com/9963132/
so that I could get this CL submitted and unblock AnalysisServer changes.

[zundel, 2012-04-03 23:26:44]

lgtm