Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
druid/.idea/inspectionProfiles/profiles_settings.xml

37 lines
1.7 KiB
XML
Raw Normal View History

Add useL2 and populateL2 configs to HybridCache (#5088) * Add useL2 and populateL2 configs to HybridCache * typo
2017-11-20 17:57:05 -05:00
<component name="InspectionProjectProfileManager">
<settings>
<option name="PROJECT_PROFILE" value="Druid" />
<version value="1.0" />
Make JavaScript and XML errors non-TeamCity errors; Update JavaScript language level to ES6 in IntelliJ settings (#7541) * Make JavaScript and XML errors non-TeamCity errors; Update JavaScript language level to ES6 in IntelliJ settings * Add license comment to assembly-2.0.0.xsd * Add .idea/README.md with comments
2019-04-25 14:21:58 -04:00
<info color="be1e0e">
<option name="BACKGROUND" value="521717" />
<option name="ERROR_STRIPE_COLOR" value="be1e0e" />
<option name="myName" value="Non-TeamCity Error" />
<option name="myVal" value="50" />
<option name="myExternalName" value="Non-TeamCity Error" />
<option name="myDefaultAttributes">
<option name="ERROR_STRIPE_COLOR" value="be1e0e" />
</option>
</info>
Introduce Non-TeamCity Warning inspection severity in IntelliJ's profile (#7499) In the IDE interface, "Non-TeamCity Warning" looks exactly like an ordinary warning, but TeamCity should be unaware of it. This may help to workaround these issues: https://youtrack.jetbrains.com/issue/IDEA-209789 and https://youtrack.jetbrains.com/issue/IDEA-209791, that block the upgrade of IntelliJ engine used in the TeamCity build. It seems like there may be a bug that leads to false positive error and the build fail in this PR: https://github.com/apache/incubator-druid/pull/6702. Removed the comment regarding "StaticPseudoFunctionalStyleMethod" inspection because the IntelliJ keeps removing it, see this issue: https://youtrack.jetbrains.com/issue/IDEA-211087
2019-04-19 09:20:08 -04:00
<info color="be9117">
<option name="BACKGROUND" value="52503a" />
<option name="ERROR_STRIPE_COLOR" value="be9117" />
<option name="myName" value="Non-TeamCity Warning" />
<option name="myVal" value="50" />
<option name="myExternalName" value="Non-TeamCity Warning" />
<option name="myDefaultAttributes">
<option name="ERROR_STRIPE_COLOR" value="be9117" />
</option>
</info>
Make JavaScript and XML errors non-TeamCity errors; Update JavaScript language level to ES6 in IntelliJ settings (#7541) * Make JavaScript and XML errors non-TeamCity errors; Update JavaScript language level to ES6 in IntelliJ settings * Add license comment to assembly-2.0.0.xsd * Add .idea/README.md with comments
2019-04-25 14:21:58 -04:00
<list size="9">
Introduce Non-TeamCity Warning inspection severity in IntelliJ's profile (#7499) In the IDE interface, "Non-TeamCity Warning" looks exactly like an ordinary warning, but TeamCity should be unaware of it. This may help to workaround these issues: https://youtrack.jetbrains.com/issue/IDEA-209789 and https://youtrack.jetbrains.com/issue/IDEA-209791, that block the upgrade of IntelliJ engine used in the TeamCity build. It seems like there may be a bug that leads to false positive error and the build fail in this PR: https://github.com/apache/incubator-druid/pull/6702. Removed the comment regarding "StaticPseudoFunctionalStyleMethod" inspection because the IntelliJ keeps removing it, see this issue: https://youtrack.jetbrains.com/issue/IDEA-211087
2019-04-19 09:20:08 -04:00
<item index="0" class="java.lang.String" itemvalue="INFORMATION" />
Make JavaScript and XML errors non-TeamCity errors; Update JavaScript language level to ES6 in IntelliJ settings (#7541) * Make JavaScript and XML errors non-TeamCity errors; Update JavaScript language level to ES6 in IntelliJ settings * Add license comment to assembly-2.0.0.xsd * Add .idea/README.md with comments
2019-04-25 14:21:58 -04:00
<item index="1" class="java.lang.String" itemvalue="Non-TeamCity Error" />
<item index="2" class="java.lang.String" itemvalue="Non-TeamCity Warning" />
<item index="3" class="java.lang.String" itemvalue="TYPO" />
<item index="4" class="java.lang.String" itemvalue="SERVER PROBLEM" />
<item index="5" class="java.lang.String" itemvalue="WEAK WARNING" />
<item index="6" class="java.lang.String" itemvalue="INFO" />
<item index="7" class="java.lang.String" itemvalue="WARNING" />
<item index="8" class="java.lang.String" itemvalue="ERROR" />
Introduce Non-TeamCity Warning inspection severity in IntelliJ's profile (#7499) In the IDE interface, "Non-TeamCity Warning" looks exactly like an ordinary warning, but TeamCity should be unaware of it. This may help to workaround these issues: https://youtrack.jetbrains.com/issue/IDEA-209789 and https://youtrack.jetbrains.com/issue/IDEA-209791, that block the upgrade of IntelliJ engine used in the TeamCity build. It seems like there may be a bug that leads to false positive error and the build fail in this PR: https://github.com/apache/incubator-druid/pull/6702. Removed the comment regarding "StaticPseudoFunctionalStyleMethod" inspection because the IntelliJ keeps removing it, see this issue: https://youtrack.jetbrains.com/issue/IDEA-211087
2019-04-19 09:20:08 -04:00
</list>
Add useL2 and populateL2 configs to HybridCache (#5088) * Add useL2 and populateL2 configs to HybridCache * typo
2017-11-20 17:57:05 -05:00
</settings>
</component>