Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Done
-
2.6
-
None
-
None
Description
Some of Ignite code style inspections are verified at Teamcity per IGNITE-9983. (Currently TC inspections are "SizeReplaceableByIsEmpty", "UnusedImport", "MissingOverrideAnnotation", "MissortedModifiers", "RedundantSuppression".)
Per discussion of issue IGNITE-10399 it looks like there is a room for improvement here. Specifically, the problem occurred because it was too difficult to find a new deviation that made TC inspections check fail because it was buried among multiple similar looking but non-critical deviations in a particular piece of old code (PageMemoryImpl.java).
It would be more convenient if programmer could easier see subset of checks that are used at Teamcity because this would allow to fix these earlier and avoid cumbersome TC runs and failure reports analysis.
Technically this could be achieved by editing inspections config file and increasing respective inspections level to ERROR. I briefly checked how it would work in a "sandbox" project on my machine and it looked quite convenient: violations of inspections used by TC were shown as red in Error Stripe while the rest remained yellow, easy to see. (It's probably not very important but for the sake of completeness a thing I noticed when testing is that having red inspections didn't block compilation and execution of the code.) Screen shot of how it worked in my experiment is attached: IDEA.inspections.TC-bot.png
Attachments
Attachments
Issue Links
- Is contained by
-
IGNITE-10422 Make {{ignite_inspection.xml}} configuration default on the project level
-
- Resolved
-
- is related to
-
IGNITE-10399 Fix inspection failures
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-