Hello Lazyweb,
Anyone have such a beast they're willing to share?
thanks,
-- peter
Hi Peter,
I just looked at your .gitignore file from github.com/.../abl_odbc_api
There you exclude .launch files. But as you have committed your .project file you are ensuring that everybody has the same project name and .launch files are reusable and helpful. In this case, I'd definitively commit .launch files as well.
The proper way not to commit launch configurations to SCM is by making them "not shared" in their settings. Then they will be burried in your .metadata folder and no SCM tool with ever care. When you opt in to share them via their settings, I'd also SCM them.
Just my PoV.
Mike
Thanks Mike.
I do usually keep the .launch files in a resources/ folder. I was holding off committing them because they contain DLC information. So there would need to be a .launch for each DLC version .... which isn't especially hard to do, now that I think of it.
-- peter
Added .launch files, per your suggestion.
-- peter