What should be in .gitignore file for a netbeans java project?

There are a fair number of files that you probably do not need to commit into git, since they are built, are generated by NB or contain environment specific information.

There are a fair number of files that you probably do not need to commit into git, since they are built, are generated by NB or contain environment specific information. If you create a project that uses Ant as the build mechanism, you usually end up with a directory tree that looks like this... project-root-directory/ + nbproject/ build-impl. Xml + private/ + project.

Properties + project. Xml + src/ + test/ + build. Xml After you do a build.. there will be a couple additional directories project-root-directory/ + build/ + dist/ + nbproject/ build-impl.

Xml + private/ + project. Properties + project. Xml + src/ + test/ + build.

Xml You should probably put the build, dist and nbproject/private directories (and their children) into your .gitignore. If you want to be very aggressive about excluding files, you may want to consider excluding all the files that appear in nbproject EXCEPT project. Properties and project.xml.

The other files in the nbproject directory are regenerated by NetBeans when the project is opened.

A very similar question was asked a year earlier and the best answer pointed to a NetBeans Knowledge Base Article that gives a similar answer as you did. – David James Sep 23 at 3:43.

There should be no NetBeans-specific files in your .gitignore. The . Gitignore file is project-specific but shared between developers, IOW there should only be things in there that are common for all developers working with the code (including ones that use OSX, Linux instead of Windows and Eclipse, IntelliJ or Notepad as editors) and that are specific to the project.

If there are some files that you would like to ignore based on your specific environment (like e.g. Windows Thumbs. Db and desktop files or NeBeans nbproject directories) you should do that in your global ignore list, not in the project-specific . Gitignore – if only because then you don't need to add them to every single of your projects individually.

If the files you want to ignore are both specific to your environment and specific to the project, put them into that repository's . Git/info/exclude.

1 Why use . Git/info/exclude rather than the projects . Gitignore?

What is the benifit / downside if put in . Gitignore? – Andrew Burns Oct 29 '10 at 19:33 @Andrew Burns The difference between .

Gitignore and . Git/info/exclude is that the former will be versioned (git tracks changes), while the latter does not. I use .

Gitignore because I sometimes change what is ignored and want that associated to version. I liked t sample . Gitignore files here.

– Ivin Aug 7 at 7:05 I disagree; it doesn't hurt an IntelliJ user if an Eclipse user checks in appropriate (e.g. Not auto-generated) project files, or vice versa. It actually can help when one member of the project team needs to work with that other IDE.(This might happen during troubleshooting or pair programming.) – David James Sep 23 at 3:41.

NetBeans specific # nbproject/private/ build/ nbbuild/ dist/ nbdist/ nbactions. Xml nb-configuration. Xml # Class Files # *.

Class # Package Files # *. Jar *. War *.ear.

There are no "files that should be" in the . Gitignore file. It is simply a matter of preference of which files you wish to be ignored by the git URL1 makes it easier for you to quickly see changes in files you care about without being cluttered with additional files.

If you are curious about the formatting of what goes in a . Gitignore you can read up on it here.

It is not "simply a matter of preference. " I will admit there is a little bit of subjectivity in this decision. But on the whole, there are widely accepted principles that will guide you most of the way there.

For example, a common maxim is that auto-generated files do not belong in the . Gitignore file. The counter-argument is that if the generation process is very slow, you might still include them.My point is that while ultimately people may disagree "on the margins," there are well-worn paths of argumentation that get people to these various points.

– David James Sep 23 at 3:33.

All files you don't want to commit into your git repository.

It's just that simple. I would suggest manually adding the ones you want in the repo, and then putting everything that's left in .gitignore. – R.

Martinho Fernandes Apr 6 '10 at 15:37 3 I think the questioner knows what the gitignore file is used for... – vkraemer Apr 6 '10 at 18:01 Yep but this question is subjective. It depends on the common sense of project's architect. There are one or one million correct answers.

– sourcerebels Apr 6 '10 at 18:33 I think there are a couple of good approaches to take. Saying that there are multiple answers, all equally valid, is wrong. (I like snarky answers when they are warranted, but this is unwarranted snarky.) – David James Sep 23 at 3:06 See the related question for some good answers: stackoverflow.

Com/questions/1267403/… – David James Sep 23 at 3:31.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.