1<module> 2<source path=""> 3 <!-- Hack to keep collect from hiding collect.testing supersource: --> 4 <exclude name="**/testing/**"/> 5</source> 6 7<!-- 8 We used to set this only for packages that had manual supersource. That 9 worked everywhere that I know of except for one place: when running the GWT 10 util.concurrent tests under Guava. 11 12 The problem is that GWT responds poorly to two .gwt.xml files in the same 13 Java package; see 14 https://groups.google.com/g/google-web-toolkit-contributors/c/CqYH59Dt_rQ/m/uVGW1QdUsXUJ 15 for details. 16 17 The summary is that it ignores one file in favor of the other. 18 util.concurrent, like nearly all our packages, has two .gwt.xml files: one 19 for prod and one for tests. However, unlike our other packages, as of this 20 writing it has test supersource but no prod supersource. 21 22 GWT happens to use the prod .gwt.xml, so it looks for no supersource for 23 tests, either. This causes it to fail to find AtomicLongMapTest. 24 25 Our workaround is to tell GWT that util.concurrent and all other packages 26 have prod supersource, even if they have none. GWT is happy to ignore us 27 when we specify a nonexistent path. 28 29 (I hope that this workaround does not cause its own problems in the future.) 30--> 31<super-source path="super"/> 32 33<inherits name="com.google.common.annotations.Annotations" /> 34<inherits name="com.google.common.base.Base" /> 35<inherits name="com.google.common.primitives.Primitives" /> 36<inherits name="com.google.gwt.core.Core" /> 37<inherits name="com.google.gwt.user.User" /> 38</module> 39