|Re: Eclipse Maven Project exporting as Maven Project [message #1800592 is a reply to message #1800567]
||Thu, 03 January 2019 05:30
| Ed Merks
Registered: July 2009
Yes, Xtext generates a lot of code, much of which you can avoid tracking. But if you don't track them, something in your Maven build will still need to generate them; you'd be best off using the Xtext forum to ask about such things:|
No, I didn't say that all the files are tracked by the MANIFEST.MF, I suggested that dependencies are tracked in this way.
In my projects that use Xtext, e.g., Xcore, these are the files I ignored:
So I mostly track all files (e.g., *.java files derived from *.xtend files, and also src-gen files) so that I don't have to generate them as part of my Maven build. And my Maven build uses Tycho so I can resolve dependencies directly from p2 repositories.
I found Git overall horribly complicated when I started, but its grown to seem intuitive. That's always the way things are. So I rarely use the command line, except when I want to script something. E.g., this script to "clean" a git repository
for i in $(echo .git */.git); do
if [ -d $i ]; then
git reset --hard
git clean -xdf
I'd suggest learning the Git UI and when something isn't comfortable, then use the command line. You don't need to use one or the other exclusively.
Powered by FUDForum
. Page generated in 0.03180 seconds