You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seem that when using the plugin in gradle, but only running a single gradle task, the GWT plugin is fired up anyway and creating folders in the configuration phase. According to gradle docs, nothing like this should happen in the configuration phase. (Sorry I don't have doc refs.)
So when I run this with gradle showRepos it automatically creates the "build" directory:
build/
└── gwt
├── cache
├── extra
├── gen
└── work
The text was updated successfully, but these errors were encountered:
Not a show stopper (for that simple task), but it is a confusing annoyance when you are trying to use another simple task to determine if a previous compile task has already run successfully and created functional output or not...and to cleanup/remove the build output dirs. (Why create empty directories in the first place?)
I'd love to send you a PR, but I don't understand the code good enough to help you out there.
It seem that when using the plugin in gradle, but only running a single gradle task, the GWT plugin is fired up anyway and creating folders in the configuration phase. According to gradle docs, nothing like this should happen in the configuration phase. (Sorry I don't have doc refs.)
So when I run this with
gradle showRepos
it automatically creates the "build" directory:The text was updated successfully, but these errors were encountered: