OpenSearch/.gitignore

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

## eclipse ignores (use 'mvn eclipse:eclipse' to build eclipse projects)
## The only configuration files which are not ignored are certain files in
## .settings (as listed below) since these files ensure common coding 
## style across Eclipse and IDEA.
## Other files (.project, .classpath) should be generated through Maven which
## will correctly set the classpath based on the declared dependencies.
.project
.classpath
eclipse-build
*/.project
*/.classpath
*/eclipse-build
/.settings/
!/.settings/org.eclipse.core.resources.prefs
!/.settings/org.eclipse.jdt.core.prefs
!/.settings/org.eclipse.jdt.ui.prefs

## 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`
initial commit 2010-02-08 08:30:06 -05:00			`work/`
fix ignore 2010-12-04 17:02:16 -05:00			`/data/`
Added plugins to .gitignore Since plugins should never be committed to the core codebase and it is useful to be able to add plugins to the development environment adding plugins folder to the .gitignore file will stop it from appearing in the unstaged changes 2014-05-28 04:38:58 -04:00			`/plugins/`
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/`
Build ElasticSearch as Debian package 2011-08-10 05:04:29 -04:00
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)`
Changed .gitignore to ignore all files in .settings except for the ones that we want to preserve, to ensure a common coding style between IDEA and Eclipse 2013-09-13 06:40:02 -04:00			`## The only configuration files which are not ignored are certain files in`
			`## .settings (as listed below) since these files ensure common coding`
			`## style across Eclipse and IDEA.`
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			`## Other files (.project, .classpath) should be generated through Maven which`
			`## will correctly set the classpath based on the declared dependencies.`
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`
adding ability for gradle to create eclipse project files and classpaths 2011-05-23 10:14:22 -04:00			`*/.project`
			`*/.classpath`
			`*/eclipse-build`
Changed .gitignore to ignore all files in .settings except for the ones that we want to preserve, to ensure a common coding style between IDEA and Eclipse 2013-09-13 06:40:02 -04:00			`/.settings/`
			`!/.settings/org.eclipse.core.resources.prefs`
			`!/.settings/org.eclipse.jdt.core.prefs`
			`!/.settings/org.eclipse.jdt.ui.prefs`
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
			`/dependency-reduced-pom.xml`