honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/dev-tools/Elasticsearch.launch

19 lines
1.4 KiB
Plaintext
Raw Normal View History

Changed pom to allow import and running from eclipse Currently when importing projects into eclipse you need to run 'mvn eclipse:eclipse' on the command line to generate the poject files. This means that when the pom changes you need to re-run the command on the command line to reflect those changes in the project in eclipse. This commit allows the developer to import the project as an existing maven project (can be shared using git after import) and then allows the application to be run inside eclipse using the .launch file in /dev-tools enabling easy debugging of the application within eclipse without requiring a maven build.
2013-11-06 15:49:21 -05:00
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication">
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS">
Fix ASL Header in source files to reflect s/ElasticSearch/Elasticsearch This commit also removes the license to Shay Banon in favor of soley Elasticsearch. Thanks Shay for this awesome product you took it far! Closes #4636
2014-01-06 16:48:02 -05:00
<listEntry value="/elasticsearch/src/main/java/org/elasticsearch/bootstrap/Elasticsearch.java"/>
Changed pom to allow import and running from eclipse Currently when importing projects into eclipse you need to run 'mvn eclipse:eclipse' on the command line to generate the poject files. This means that when the pom changes you need to re-run the command on the command line to reflect those changes in the project in eclipse. This commit allows the developer to import the project as an existing maven project (can be shared using git after import) and then allows the application to be run inside eclipse using the .launch file in /dev-tools enabling easy debugging of the application within eclipse without requiring a maven build.
2013-11-06 15:49:21 -05:00
</listAttribute>
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES">
<listEntry value="1"/>
</listAttribute>
Eclipse: Fix launch configuration We had a file in dev-tools/ElasticSearch.launch which tried to launch elasticsearch but failed somewhat epically because of the security manager and files having moved. This recreates it with `-Des.security.manager.enabled=false` to get it working again. Its not as nice as testing with the security manager in place but its better than waiting minutes for maven to package and startup elasticsearch.
2015-08-21 17:00:55 -04:00
<listAttribute key="org.eclipse.debug.ui.favoriteGroups">
<listEntry value="org.eclipse.debug.ui.launchGroup.debug"/>
<listEntry value="org.eclipse.debug.ui.launchGroup.run"/>
</listAttribute>
<booleanAttribute key="org.eclipse.jdt.launching.ATTR_USE_START_ON_FIRST_THREAD" value="true"/>
Fix ASL Header in source files to reflect s/ElasticSearch/Elasticsearch This commit also removes the license to Shay Banon in favor of soley Elasticsearch. Thanks Shay for this awesome product you took it far! Closes #4636
2014-01-06 16:48:02 -05:00
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="org.elasticsearch.bootstrap.Elasticsearch"/>
Eclipse: Fix launch configuration We had a file in dev-tools/ElasticSearch.launch which tried to launch elasticsearch but failed somewhat epically because of the security manager and files having moved. This recreates it with `-Des.security.manager.enabled=false` to get it working again. Its not as nice as testing with the security manager in place but its better than waiting minutes for maven to package and startup elasticsearch.
2015-08-21 17:00:55 -04:00
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="start"/>
Changed pom to allow import and running from eclipse Currently when importing projects into eclipse you need to run 'mvn eclipse:eclipse' on the command line to generate the poject files. This means that when the pom changes you need to re-run the command on the command line to reflect those changes in the project in eclipse. This commit allows the developer to import the project as an existing maven project (can be shared using git after import) and then allows the application to be run inside eclipse using the .launch file in /dev-tools enabling easy debugging of the application within eclipse without requiring a maven build.
2013-11-06 15:49:21 -05:00
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="elasticsearch"/>
Fix test for _cat/nodeattrs Adds a node attribute to all test runs and uses the attribute to test `_cat/nodeattrs`. Note that its quite possible create an impressively slow regex while doing this and you have to be careful. See comment in commit for more if curious. Closes #12558
2015-08-28 14:46:33 -04:00
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Xms256m -Xmx1g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=logs/heapdump.hprof -Delasticsearch -Des.foreground=yes -ea -Des.path.home=target/eclipse_run -Des.security.manager.enabled=false&#10;-Des.node.attr=test"/>
Changed pom to allow import and running from eclipse Currently when importing projects into eclipse you need to run 'mvn eclipse:eclipse' on the command line to generate the poject files. This means that when the pom changes you need to re-run the command on the command line to reflect those changes in the project in eclipse. This commit allows the developer to import the project as an existing maven project (can be shared using git after import) and then allows the application to be run inside eclipse using the .launch file in /dev-tools enabling easy debugging of the application within eclipse without requiring a maven build.
2013-11-06 15:49:21 -05:00
</launchConfiguration>