search

tbroyer / gwt-maven-plugin

Starting fresh on building GWT projects with Maven
https://tbroyer.github.io/gwt-maven-plugin/
Apache License 2.0
166 stars 39 forks source link

gwt-app should optionally publish a "deploy" artifact #9

Open tbroyer opened 11 years ago

tbroyer commented 11 years ago

Currently, the generated -deploy files are lost. It should be possible to have them in a JAR, ZIP or WAR with a deploy classifier so you can use e.g. stacktrace deobfuscation.

Workaround: use the maven-assembly-plugin.

ghost commented 6 years ago

Hello,

are there any plans to solve and release this enhancement?

tbroyer commented 6 years ago

No short-term plan, no. Please experiment with the maven-assembly-plugin and report your experience here (should this be a ZIP? a JAR? how do you actually use it? etc.)

ghost commented 6 years ago

We have multi-module projects, where the shared project is build as gwt-lib and client project as gwt-app. The server project creates an overlay war artifact based on client.war. We always need the symbolMaps for stacktrace deobfuscation in our final server.war, otherwise we cannot get a hint where client exception has been thrown. We now use the maven-resources-plugin configured just before your gwt-maven-plugin in prepare-package phase to copy gwt/deploy folder to the root of client.war before it is packaged. Our RemoteLoggingService reads the symbolMaps from root of the final war and everything works as before.

Perhaps this is not the intent of this issue, but it works. The only thing to change in your plugin is to also package the gwt/deploy folder in the client.war.

tbroyer commented 6 years ago

Or maybe you could “just” configure the plugin with:

    <deploy>${project.build.directory}/${project.build.finalName}</deploy>

instead of the ${project.build.directory}/gwt/deploy default value: https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html#deploy

ghost commented 6 years ago

Also works and is a little bit smarter! Thank you!