OpenSearch/.gitignore


# intellij files
.idea/
*.iml
*.ipr
*.iws

# eclipse files
.project
.classpath
eclipse-build
.settings

# netbeans files
nb-configuration.xml
nbactions.xml

# gradle stuff
.gradle/
build/
generated-resources/

# maven stuff (to be removed when trunk becomes 4.x)
*-execution-hints.log
target/
dependency-reduced-pom.xml

# testing stuff
**/.local*
.vagrant/

# osx stuff
.DS_Store

# random old stuff that we should look at the necessity of...
docs/html/
docs/build.log
html_docs
/tmp/
backwards/
Organize and annotate gitignores 2015-12-15 21:51:38 -05:00
			`# intellij files`
update .gitignore 2011-12-05 18:11:12 -05:00			`.idea/`
			`*.iml`
ignore intellij project/workspace files closes #9044 2014-12-23 02:05:01 -05:00			`*.ipr`
			`*.iws`
[Packaging] Run tests in vagrant This creates a module in qa called vagrant that can be run if you have vagrant and virtualbox installed and will run the packaging tests in trusty and centos-7.0. You can ask it to run tests in other linuxes. This is the full list: * precise aka Ubuntu 12.04 * trusty aka Ubuntu 14.04 * vivid aka Ubuntun 15.04 * wheezy aka Debian 7, the current debian oldstable distribution * jessie aka Debian 8, the current debina stable distribution * centos-6 * centos-7 * fedora-22 * oel-7 There is lots of documentation on how to do this in the TESTING.asciidoc. Closes #12611 2015-08-04 09:36:22 -04:00
Organize and annotate gitignores 2015-12-15 21:51:38 -05:00			`# eclipse files`
adding ability for gradle to create eclipse project files and classpaths 2011-05-23 10:14:22 -04:00			`.project`
			`.classpath`
Use a separate build directory for Eclipse. The fact that Maven and Eclipse share the same build directories can trigger race conditions when both are trying to build at the same time, eg. if you run `mvn clean test` while Eclipse is up and running: Eclipse will notice that some class files are missing and start compiling in parallel with Maven. 2013-08-29 04:26:06 -04:00			`eclipse-build`
Consolidate .gitignore entires for eclipse Rather than specify paths for the .gitignored files that Eclipse uses for project management just ignore all files and directories that look like those directories. That way we can add new subprojects and we won't need add more .gitignore entries. 2015-07-28 18:13:02 -04:00			`.settings`
added netbeans ignores 2011-12-08 03:47:07 -05:00
Organize and annotate gitignores 2015-12-15 21:51:38 -05:00			`# netbeans files`
added netbeans ignores 2011-12-08 03:47:07 -05:00			`nb-configuration.xml`
			`nbactions.xml`
Add info to _cat/nodes, add _cat/indices. 2013-07-15 16:28:38 -04:00
Organize and annotate gitignores 2015-12-15 21:51:38 -05:00			`# gradle stuff`
			`.gradle/`
			`build/`
			`generated-resources/`
Build: Update gitignore to keep maven targets on master See #14364 2015-10-29 18:55:41 -04:00
Organize and annotate gitignores 2015-12-15 21:51:38 -05:00			`# maven stuff (to be removed when trunk becomes 4.x)`
Build: Update gitignore to keep maven targets on master See #14364 2015-10-29 18:55:41 -04:00			`*-execution-hints.log`
			`target/`
Organize and annotate gitignores 2015-12-15 21:51:38 -05:00			`dependency-reduced-pom.xml`

			`# testing stuff`
			`*/.local`
			`.vagrant/`

			`# osx stuff`
			`.DS_Store`

			`# random old stuff that we should look at the necessity of...`
			`docs/html/`
			`docs/build.log`
			`html_docs`
			`/tmp/`
			`backwards/`