Re: BUG? GWT modules inherit: filepath vs classpath
On 10/26/13 12:16, Thomas Broyer wrote: Modules can specify which subpackages contain translatable /source/, causing the named package and its subpackages to be added to the /source path/. Only files found on the source path are candidates to be translated into JavaScript, making it possible to mix client-side http://www.gwtproject.org/doc/latest/DevGuideCodingBasics.html#DevGuideClientSide http://www.gwtproject.org/doc/latest/DevGuideCodingBasics.html#DevGuideClientSide and server-side http://www.gwtproject.org/doc/latest/DevGuideServerCommunication.html#DevGuideServerSide http://www.gwtproject.org/doc/latest/DevGuideServerCommunication.html#DevGuideServerSide code together in the same classpath without conflict. --- so the behavior looks inconsistent with the documentation (bug?) What do you find inconsistent? The doc talks about the named package and its subpackages and classpath, and that's the behavior you described too (which is expected, as Jens already said) -- Thanks for clearing this out. It is good to know that it is intended behavior. What do I find inconsistent? The documentation says Only files found on the source path... and .gwt.xml I thought/hope relative filepath was specified and not classpath. So I would propose the following change -Only files found on the source path are candidates +Only files found on the source classpath are candidates ... +Note: If you are merging classes from multiple projects on the same package structure and you have one .gwt.xml specifying a classpath in one of the projects all classes in that classpath (from multiple projects) are candidates to be translated in javascript. Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: BUG? GWT modules inherit: filepath vs classpath
No, the source path is a subset of the classpath (defined by the source elements in gwt.XML files). It's defined in terms of packages, not file paths. Le 28 oct. 2013 21:03, Vassilis Virvilis vasv...@gmail.com a écrit : On 10/26/13 12:16, Thomas Broyer wrote: Modules can specify which subpackages contain translatable /source/, causing the named package and its subpackages to be added to the /source path/. Only files found on the source path are candidates to be translated into JavaScript, making it possible to mix client-side http://www.gwtproject.org/**doc/latest/**DevGuideCodingBasics.html#* *DevGuideClientSidehttp://www.gwtproject.org/doc/latest/DevGuideCodingBasics.html#DevGuideClientSide http://www.gwtproject.org/**doc/latest/**DevGuideCodingBasics.html#* *DevGuideClientSidehttp://www.gwtproject.org/doc/latest/DevGuideCodingBasics.html#DevGuideClientSide and server-side http://www.gwtproject.org/**doc/latest/** DevGuideServerCommunication.**html#DevGuideServerSidehttp://www.gwtproject.org/doc/latest/DevGuideServerCommunication.html#DevGuideServerSide http://www.gwtproject.org/**doc/latest/** DevGuideServerCommunication.**html#DevGuideServerSidehttp://www.gwtproject.org/doc/latest/DevGuideServerCommunication.html#DevGuideServerSide code together in the same classpath without conflict. --- so the behavior looks inconsistent with the documentation (bug?) What do you find inconsistent? The doc talks about the named package and its subpackages and classpath, and that's the behavior you described too (which is expected, as Jens already said) -- Thanks for clearing this out. It is good to know that it is intended behavior. What do I find inconsistent? The documentation says Only files found on the source path... and .gwt.xml I thought/hope relative filepath was specified and not classpath. So I would propose the following change -Only files found on the source path are candidates +Only files found on the source classpath are candidates ... +Note: If you are merging classes from multiple projects on the same package structure and you have one .gwt.xml specifying a classpath in one of the projects all classes in that classpath (from multiple projects) are candidates to be translated in javascript. Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: BUG? GWT modules inherit: filepath vs classpath
On Friday, October 25, 2013 11:20:50 PM UTC+2, Vassilis Virvilis wrote:
Hi everybody,
I have the following situation
There are 3 projects. Let's call them application_project,
library_project, datatype_project.
The application_project depends on the other two. However only the
datatype_project project is supposed to be compiled to javascript. So
the there is a .gwt.xml inside the datatype_project.
Now the problem is that library_project and datatype_project have the
same package structure. So the unified tree looks like
com.company.lib.{dir1/,dir2/ from library_project, datatype/ from
datatype_project}
The gwt.xml inside datatype_project is located at com.company and has
contents
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit
2.5.1//EN
http://google-web-toolkit.googlecode.com/svn/tags/2.5.1/distro-source/core/src/gwt-module.dtd;
module
inherits name=com.google.gwt.user.User /
source path=lib/source
/module
The problem is that the gwt compiler is trying to compile staff from the
library_project just because the classpath is matching
(com.company.lib). I thought that the source path= directive was about
files and directories and not classpath. Finally in
http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html#DevGuideModules
there is the following statement.
---
Source Path
Modules can specify which subpackages contain translatable /source/,
causing the named package and its subpackages to be added to the /source
path/. Only files found on the source path are candidates to be
translated into JavaScript, making it possible to mix client-side
http://www.gwtproject.org/doc/latest/DevGuideCodingBasics.html#DevGuideClientSide
and server-side
http://www.gwtproject.org/doc/latest/DevGuideServerCommunication.html#DevGuideServerSide
code together in the same classpath without conflict.
---
so the behavior looks inconsistent with the documentation (bug?)
What do you find inconsistent? The doc talks about the named package and
its subpackages and classpath, and that's the behavior you described too
(which is expected, as Jens already said)
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
Re: BUG? GWT modules inherit: filepath vs classpath
Thats expected. The GWT compiler scans it's classpath during compilation and thus it can not have any notion of projects. Change your gwt.xml to source path=datatype / or source path=lib/datatype / depending if you want to relocate your Datatype.gwt.xml to com/company/lib or not. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
