On Friday, 10 August, 2012 at 10:34 AM, Thomas Broyer wrote:
Are the JARs exported by the common Eclipse project?
They aren't -- both M2E or eclipse:eclipse handles transitive dependencies by
adding the JARs to the class path of the 'child' project, so you don't need the
'parent' to export,
Are the JARs exported by the common Eclipse project?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/xZ4Ve-ZuQdAJ.
To post to this group, send
Hi,
- That split isn't perfect yet, but I can't seem to get Eclipse to launch
the project. If I launch the project through mvn gwt:run, it launches
successfully, but if I launch it through Eclipse (Run As Web Application)
the server part fails to start up when a filter can't find the SLF4J
I have a 2yo GWT project that's getting a little big for a single module,
and we're bringing in a new project and we'd like to share some code.
Accordingly, I've split the project into a 'common' codebase and a
project-specific codebase. That split isn't perfect yet, but I can't seem
to get
