OpenSearch/.gitignore

.idea/
.gradle/
*.iml
*.ipr
*.iws
work/
/data/
logs/
.DS_Store
build/
target/
*-execution-hints.log
docs/html/
docs/build.log
/tmp/
backwards/
html_docs
.vagrant/

## eclipse ignores (use 'mvn eclipse:eclipse' to build eclipse projects)
## All files (.project, .classpath, .settings/*) should be generated through Maven which
## will correctly set the classpath based on the declared dependencies and write settings
## files to ensure common coding style across Eclipse and IDEA.
.project
.classpath
eclipse-build
.settings

## netbeans ignores
nb-configuration.xml
nbactions.xml

dependency-reduced-pom.xml
update .gitignore 2011-12-05 18:11:12 -05:00			`.idea/`
initial commit 2010-02-08 08:30:06 -05:00			`.gradle/`
update .gitignore 2011-12-05 18:11:12 -05:00			`*.iml`
ignore intellij project/workspace files closes #9044 2014-12-23 02:05:01 -05:00			`*.ipr`
			`*.iws`
initial commit 2010-02-08 08:30:06 -05:00			`work/`
fix ignore 2010-12-04 17:02:16 -05:00			`/data/`
add data and logs to git ignore 2010-11-03 15:42:36 -04:00			`logs/`
initial commit 2010-02-08 08:30:06 -05:00			`.DS_Store`
			`build/`
update .gitignore 2011-12-05 18:11:12 -05:00			`target/`
Update .gitignore to ignore the execution hints files 2014-03-28 04:59:07 -04:00			`*-execution-hints.log`
Migrated documentation into the main repo 2013-08-28 19:24:34 -04:00			`docs/html/`
			`docs/build.log`
Ignore project tmp dir. 2013-11-01 17:40:14 -04:00			`/tmp/`
[TEST] Add basic Backwards Compatibility Tests This commit add a basic infrastructure as well as primitive tests to ensure version backwards compatibility between the current development trunk and an arbitrary previous version. The compatibility tests are simple unit tests derived from a base class that starts and manages nodes from a provided elasticsearch release package. Use the following commandline executes all backwards compatiblity tests in isolation: ``` mvn test -Dtests.bwc=true -Dtests.bwc.version=1.2.1 -Dtests.class=org.elasticsearch.bwcompat.* ``` These tests run basic checks like rolling upgrades and routing/searching/get etc. against the specified version. The version must be present in the `./backwards` folder as `./backwards/elasticsearch-x.y.z` 2014-05-14 11:52:02 -04:00			`backwards/`
Docs: Mapping docs completely rewritten for 2.0 2015-08-06 11:24:29 -04:00			`html_docs`
[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			`.vagrant/`

Put Eclipse settings in the root directory. This enforces that settings are taken into account whichever mean is used to import the project into Eclipse (manual import, m2e, mvn eclipse:eclipse, ...). 2013-06-26 10:51:47 -04:00			`## eclipse ignores (use 'mvn eclipse:eclipse' to build eclipse projects)`
Adds eclipse settings files to set correct encoding and complier preferences This is done in the maven-eclipse-plugin so now all eclipse files are generated by mV eclipse:eclipse and can safely be ignored 2015-06-08 09:39:17 -04:00			`## All files (.project, .classpath, .settings/*) should be generated through Maven which`
[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			`## will correctly set the classpath based on the declared dependencies and write settings`
Adds eclipse settings files to set correct encoding and complier preferences This is done in the maven-eclipse-plugin so now all eclipse files are generated by mV eclipse:eclipse and can safely be ignored 2015-06-08 09:39:17 -04:00			`## files to ensure common coding style across Eclipse and IDEA.`
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
			`## netbeans ignores`
			`nb-configuration.xml`
			`nbactions.xml`
Add info to _cat/nodes, add _cat/indices. 2013-07-15 16:28:38 -04:00
Ignore dependency-reduced-pom.xml even if used in submodules 2015-05-26 10:26:03 -04:00			`dependency-reduced-pom.xml`