SourceMaps and production builds

[tbroyer]

SourceMaps and production builds

[tbroyer]

• you could point -saveSourceOutput to your ${project.build.directory}/${project.finalName} (or whatever value you configured for webappDirectory) or a subdirectory to have it packaged into your gwt-app artifact (you could also use resources:copy-resources during the prepare-package phase if you liked); or you could point -saveSourceOutput to some path ending in .war or .zip (.jar also works) to get sources to a single archive and then use build-helper-maven-plugin to attach it as a secondary artifact that you could then integrate into your final WAR as an overlay.
• gwtproject/gwt#6014 was a different issue (or actually, the same underlying issue, but at a different place, so fixed only there – well, -saveSource didn't actually exist at the time, so let's say "reintroduced at a different place"). Please open an issue over GWT. BTW, I don't think it'd happen if your output is a WAR/ZIP/JAR rather than a directory.

Anyway, closing as this is not directly related to the plugin.

[timeu]

Ok great thanks for listing the options.
Originally I tried to output it to ${project.build.directory}/${project.finalName} but ran into the "file to long" issue.
I will try the .war option and create an issue over at GWT.