Re: SuperDevMode does not see sources from another project (Eclipse)

Am Donnerstag, 10. Dezember 2015 11:37:32 UTC+1 schrieb Gordan Krešić:

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?

Add -src ${resource_loc:/LibProj}/src/main/java to gwt_debug

launch configuration. See how related SDM issue was fixed in

Gerrit Code Review: [1].

* [1] https://gerrit-review.googlesource.com/68971

--
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 google-web-toolkit+unsubscribe@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/d/optout.