-
Notifications
You must be signed in to change notification settings - Fork 33
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
Better handling of output folders in example project #10
Comments
Yes it is, because we currently don't know whether we have to treat an output folder as a Java source folder or not. |
Ok, I see, thanks :) Still, in the example pom here, I think it would be best to separate the output folders for xtend from those for hero. |
Hi, A little feedback on that bug I opened a long time ago. On the first point, it seems that now (or maybe even before and I misunderstood how things worked at that time) xtend is generated to src/main/xtend-gen without having to explicitly configure it in the pom.xml, while the hero language is generated to src/main/generated-sources/xtend/. On the second point, I have nothing to add except that the xtend-gen folder is not cleaned while the folder where hero files are generated is.
(edit: I had forgotten the test directories) |
Hi,
Would be best if the example project was using two different output folders for xtend and the hero language.
And by the way, I'm surprised that one has to explicitly tell maven to add the source folder of xtend (or hero?) and to clean it...
I know that with the xtend-maven-plugin there is no need for that, is that needed for xtext-maven-plugin? If yes... why? :)
The text was updated successfully, but these errors were encountered: