Yep. I added src-demo. My GWT_HOME points to
gwt-trunk/build/staging/gwt-windows-0.0.0

Trying to start DatePickerDemo I get this in the console:

com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
        at 
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:334)
        at 
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$1(ReflectiveParser.java:282)
        at 
com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:381)
        at 
com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:243)
        at 
com.google.gwt.dev.cfg.ModuleDefSchema$BodySchema.__inherits_begin(ModuleDefSchema.java:212)
<snip>

Curiously enough, there is no previous log entry. The
UnableToCompleteException appears twice followed by:

com.google.gwt.core.ext.typeinfo.NotFoundException: java.lang.Object
at com.google.gwt.core.ext.typeinfo.TypeOracle.refresh(TypeOracle.java:544)
        at 
com.google.gwt.dev.javac.TypeOracleMediator.refresh(TypeOracleMediator.java:394)
        at 
com.google.gwt.dev.javac.CompilationState.compile(CompilationState.java:137)
        at com.google.gwt.dev.cfg.ModuleDef.updateTypeOracle(ModuleDef.java:470)
        at com.google.gwt.dev.cfg.ModuleDef.getTypeOracle(ModuleDef.java:324)
        at 
com.google.gwt.dev.GWTShell$BrowserWidgetHostImpl.createModuleSpaceHost(GWTShell.java:252)
        at 
com.google.gwt.dev.shell.ie.BrowserWidgetIE6$External.gwtOnLoad(BrowserWidgetIE6.java:72)
        at 
com.google.gwt.dev.shell.ie.BrowserWidgetIE6$External.invoke(BrowserWidgetIE6.java:139)
        at 
com.google.gwt.dev.shell.ie.IDispatchImpl.Invoke(IDispatchImpl.java:294)
        at 
com.google.gwt.dev.shell.ie.IDispatchImpl.method6(IDispatchImpl.java:194)
<snip>

The GWT shell complains about missing:

com/google/gwt/dev/jjs/intrinsic/Intrinsic.gwt.xml
com/google/gwt/emul/EmulationWithUserAgent.gwt.xml
and java.lang.Object (repeatedly)

I'm guessing the XML parsing is at the root of all this, so I'll dig
around there. If this rings any bells, though, I'd love to hear about
it.



On Fri, Sep 26, 2008 at 3:38 PM, Emily Crutcher <[EMAIL PROTECTED]> wrote:
> src-demo is a new source root that must be added if you are using your own
> launch configs.
>
> If you are using the checked in launch configs, one change is that  GWT_HOME
> is assumed to point to a distribution, i.e. a gwt built with ant dist rather
> then ant build.
>
> On Fri, Sep 26, 2008 at 3:34 PM, Isaac Truett <[EMAIL PROTECTED]> wrote:
>>
>> Thank you both! I'll see if I can get those launch configs running in
>> Eclipse. Everything compiles, but there's something amiss in my
>> runtime classpath.
>>
>>
>>
>>
>> On Fri, Sep 26, 2008 at 1:53 PM, Emily Crutcher <[EMAIL PROTECTED]> wrote:
>> > Also, I'm starting to add eclipse launch configs for the demos in
>> >    trunk\eclipse-experimental\incubator-resources-windows
>> > and
>> >    trunk\eclipse-experimental\incubator-resources-linux
>> >
>> > On Fri, Sep 26, 2008 at 1:47 PM, John LaBanca <[EMAIL PROTECTED]>
>> > wrote:
>> >>
>> >> BYOB for now, but let us know if you have trouble configuring it to run
>> >> in
>> >> your favorite IDE.  We'll probably have to add a build rule to the
>> >> build.xml
>> >> file at some point.
>> >>
>> >> Thanks,
>> >> John LaBanca
>> >> [EMAIL PROTECTED]
>> >>
>> >>
>> >> On Fri, Sep 26, 2008 at 1:27 PM, Isaac Truett <[EMAIL PROTECTED]>
>> >> wrote:
>> >>>
>> >>> Is there a mechanism currently in SVN for building the gen2 demos in
>> >>> src-demo? I don't see shell scripts, batch files, etc. or anything in
>> >>> build.xml. Is it BYOB at this point?
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > "There are only 10 types of people in the world: Those who understand
>> > binary, and those who don't"
>> >
>> > >
>> >
>>
>>
>
>
>
> --
> "There are only 10 types of people in the world: Those who understand
> binary, and those who don't"
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Reply via email to