Community
Participate
Working Groups
JDT tests are prone to raising compile warnings, whenever we move to the next AST level. For latest see https://www.eclipse.org/lists/jdt-dev/msg01056.html I believe DOM/Model tests basically have a strategy to minimize maintenance, but since this strategy is not clearly documented, each version bump may introduce workarounds here and there, thus blurring the picture. In this bug I'd like to capture a smoothly maintainable strategy for future versions. Questions: - Which tests should update to latest AST level, once available? - Which tests should be frozen to the AST level of their original purpose? - What is the purpose and scope of - AbstractJavaModelTest.AST_INTERNAL_JLSx ? - ConverterTestSetup.JLSx_INTERNAL ? - ConverterTestSetup.getJLSx() ? - AbstractASTTests.testLevel ? As a result I'd like to see two simple HOWTOs: - What adjustments are needed in existing tests to embrace a new AST level? - What is the pattern for creating tests for a new AST level specifically?
Bulk move out of 4.14
Bulk move out of 4.16
Bulk move out of 4.19 M1
Removing the target milestone as we don't have any owner of this bug.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
