-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packaging for gwt-app misses Web application sources and overlays #8
Comments
This is on-purpose: you're supposed to use a |
Thanks for pointing this out. I've done this and observed the following:
Example:
To me this looks like a deviation from what Maven intends regarding transitive dependency resolution. Is this intentional or did I overlook something here? |
GWT has a mechanism for publishing static files: its public source ( Ideally a AFAICT, Please come provide feedback on issue #2, but given the above, I start to think that a WAR overlay is the least bad of our choices here. |
Hmm, I got the impression that the new I'm not generally opposing configuration. In fact, I think it's better to have configuration than poorly documented or weakly understood conventions which seem to be at the root of many problems people are experiencing with the Maven ecosystem (me included). However, what I'd like to avoid is having configuration spread all over the place. In this case, I'd prefer to configure the module structure in Maven only. Anyway, as a workaround, I appreciate your hint on the publishing mechanism. In my recent feedback on issue #2, I've already described a different view on what should comprise a Regarding the Atmosphere jQuery dependency, I take your point that it should be declared in the module where the HTML host page lives. On possible dependency conflicts with bundled jQuery instances, I agree that nothing good happens after midnight. It seems that Atmosphere is moving towards jQuery-free implementations though, so I might get some relief for free ;-). |
Static webapp sources and war overlays (dependencies with
<type>war</type>
and<scope>runtime</scope>
) should be included in agwt-app
package. Packaging should essentially be compatible with the Maven war plugin to honor The Maven Way™.These capabilities are currently missing in the plugin. In addition, there are no configuration options to include additional files in the archive.
Use case:
gwt-app
.The text was updated successfully, but these errors were encountered: