Monday, April 3, 2017

Re: How to deal with transitive maven dependencies?

Hello Thomas,

sorry for the late answer...

Since my app works when doing everything on the command line, the only thing I want is that the error markers disappear (assuming that they are false positives)...

Then all you should have to do is telling Eclipse to stop resolving dependencies from the workspace (and only from the local repository).
IIRC, right-click on the project,→ Maven → uncheck the menu item talking about resolving from the workspace.

That was it! The error markers are gone! But I don't understand exactly what's going on here. Why do I see the MojoExecutionException when resolving dependencies is enabled? 
 
It seems strange to me though that Eclipse would try to package the project, did you change the preferences of goals Eclipse should run on project import or when updating project configuration?

No, I simply created the project with webAppCreator and selected "Import maven project"...

Assuming you have a folder "project" containing two subfolders "lib" and "app" containing your library and application projects respectively, then create a pom.xml in "project" with <packaging>pom</packaging> and this snippet:
<modules>
  <module>lib</module>
  <module>app</module>
</modules>
Then run all your Maven commands in the "project" folder (never in the "lib" or "app" subfolders).

Ok, sounds good.
I tried this with a pom containing only what you said, bur maven is missing groupId, artifactId and that. What would you call the groupId abd artifactId here?
 
Magnus

--
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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment