It's all about the answers!

Ask a question

Jazzignore exclude files

Yaron Norani (47267065) | asked Nov 19 '14, 5:49 a.m.
retagged Nov 19 '14, 10:10 a.m. by Evan Hughes (2.4k1318)

We need a solution for the following scenario:
1. Would like to ignore all   .exe  files located in dir1.
2. Still, would like to be able to manage 3 files with same  .exe extension.
3. For the 3 files would like to be able to detect future changes through the pending changes view.

We have managed #1 and #2.
How can we achieve #3 ?



Evan Hughes commented Nov 19 '14, 10:09 a.m.

Are all of the files in dir1?

Yaron Norani commented Nov 19 '14, 10:15 a.m.

 Yes. All in dir1. 

2 answers

permanent link
Evan Hughes (2.4k1318) | answered Nov 19 '14, 11:04 a.m.
You should either:
1. copy the .exe files you care about out of the ignored directory as part of your build process
2. create precise ignore rules that ignore the .exe files you don't want in source control, but allow the three files you want into source control.

permanent link
Joshua Small (11) | answered Apr 16 '15, 10:47 a.m.
I chatted with Evan about a more specific issue we were having, and wanted to include the chat transcript for reference:

The summary is we were using a combination of standards and tools that placed certain restrictions on what we wanted to ignore and include, with some files being right next to each other.  Tools can change more than an accepted standard can, but ultimately our problem was just that because of the standard(s) we are working with, and also wanting the convenience of using a single recursive ignore rule.

I do agree that the general solution is to separate generated/intermediate/derived files/build artifacts from the source tree so that inclusion and exclusion are more obvious.  The problem in our case is that we have marked certain files that are needed to be read as source by Eclipse in order to work with them properly as such.
We could attempt to change the tool by marking the derived bit as Evan had also suggested, which would work with the specific program better, acting as the next layer above the source and build files, and we could also tweak our recursive ignore rule slightly without having to add several explicit entries if we were to remove the recursive ignore rule entirely.

Still, the best possible solution to work with source control repositories and the concept of using these ignore files remains, is to separate the build and source trees.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.