Maybe not a warning, but maybe an INFO-level log entry, or perhaps a TRACE-level one. I think the default introduction of source path="client" is net confusing. Forcing people to specify it would have helped (forced?) people to understand what is going on.
On Mon, Nov 23, 2009 at 1:40 PM, John Tamplin <j...@google.com> wrote: > On Mon, Nov 23, 2009 at 1:33 PM, Matt Mastracci <matt...@mastracci.com>wrote: > >> I'll work around the implicit source path issue for now by using fake >> source paths in modules that don't have any additional source >> imports. If possible, it would be useful if there were a log warning >> explaining that the source path is defaulting to "client". >> > > I don't think that warning there would be good, as that is a pretty common > default - basically if you are using the recommended package setup and you > don't have server-shared code, the common case is not needing any <source> > tag in your module. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors