java - GWT 1.6 project war layout- mixing source code & compiler-generated artifacts? -
After wrapping a GWT-1.5 project, I see what we have to do to migrate to 1.6 I I am very surprised to see that GWT wants to write its compiled output in war directory, where normally you will have items in source control.
What is the reason behind this? Did Google really think it was a good idea? Is compiler-built artwork an alternative way to keep the source code separate?
Edit :
It has been suggested that I specify the -war option to the output directory. I have written some ANNT scripts, and it is mostly working, I have to copy in my directory of the static resources such as HTML, JSP, etc. (I target / war, maven-style) I am using Is this what most people are doing? Or do you just write GWT in your source-code-controlled war DIR and telling your VCS to ignore non-version-controlled files? It happened to me that GWT could have some advantage to write directly on this diary, since then the JT can automatically notice changes in JSP, HTML etc., and avoid making a copy to show these changes for.
Use the "-world" option to control the output.
FYI: Wiki is near what you are hoping for, what they were thinking, would give you some insight.
Also see if there are some things along with new project layouts to discuss with this change. / P>
Comments
Post a Comment