Suppose I have one library (configured in Eclipse as standalone project - LibProj) and one application (configured in Eclipse as separate project - AppProj) that uses that library.
During regular application development, I include library's .jar with classes and sources and that works flawlessly. However, while maintaining a library (e.g. adding feature that application uses), I find it useful to add LibProj on AppProj's build path and then hack on both sources without rebuilding library's jar every time. This works for regular Java code, but when I try to invoke SuperDevMode for a module that uses some stuff from library, SDM complains that it can not find sources for used classes. In Eclipse I have no problems compiling AppProj - it sees classes from LibProj, so problem is obviously in sources for that classes. What I did: * placed LibProj on AppProj's build path (AppProj -> Properties -> Java Build Path -> Projects) * made sure that debug configuration that launches SDM has LibProj on classpath (tab Classpath in debug configuration settings) * made sure that debug configuration that launches SDM has LibProj sources available (tab Sources in debug configuration settings) What am I missing? Eclipse Mars.1 (4.5.1) Java 7 GWT 2.7 Google Plugin for Eclipse 4.4 (0.0.0.201512080655) If it makes any difference both LibProj and AppProj are Gradle projects (I use Buildship 1.0.6.v20151126-1638 for Eclipse-Gradle integration). -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
