blocks|key|3031527|text|您可以在IntelliJ中进行批量更改，以更改每个字段、局部变量或参数，这些字段、局部变量或参数可能是最终的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3031528|使用选项进行代码分析，并全局“应用修复”，确保它仍然可以编译，因为在一些奇怪的情况下，它并不总是100%25正确。|3031529|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You can do a bulk change in IntelliJ to change every field, local variable or parameter which can be final to be final.

Do a Code Analysis with the option, and "Apply Fix" globally, make sure it still compiles as it doesn't always get it 100% right in odd cases.

blocks|key|748485|text|我不知道Eclipse或NetBeans中有这样的重构。但是一个像样的正则表达式替换就可以做到这一点。为了确保您不会意外地在不应该发生的地方执行它，您可能需要手动确认每个替换。但是，如果您有数百个类，这可能是不可行的。在这种情况下，到处进行替换，然后检查与旧版本的差异可能是有用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|748486|如果任何参数因为被覆盖而不是最终的，那么它将在编译过程中变得清晰。|748487|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I don't know of any such refactoring in Eclipse or NetBeans. But a decent regular expression replace would do the trick. In order to make sure you don't accidentally perform it in places where it shouldn't happen, you might want to confirm each replace manually. This might not really be feasible if you have hundreds of classes, though. In that case, doing the replace everywhere and then checking a diff with the older version could be of use.

Should any argument not be made final because it is overwritten, it'll become clear during compilation.

blocks|key|4646770|text|正如Peter+Lawrey所建议的，IntelliJ做到了这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4646771|Analyze+->+Inspect+code+->自定义配置文件|4646772|在"Code+style+issues“一节中，您有：|4646773|字段可能是最终的|offset|length|style|BOLD|4646774|This+inspection+reports+any+fields+which+may+safely+be+made+final.+A+static+field+may+
be+final+if+it+is+initialized+in+its+declaration+or+in+one+static+class+initializer,+but+
not+both.+A+non-static+field+may+be+final+if+it+is+initialized+in+its+declaration+or+in+
one+non-static+class+initializer+or+in+all+constructors.
Powered+by+InspectionGadgets|code-block|syntax|javascript|4646775|局部变量或参数可以是最终的|4646776|This+inspection+reports+parameters+or+local+variables,+found+in+the+specified+inspection
scope,+that+may+have+a+final+modifier+added.

Use+check+boxes+in+the+inspection+options+below,+to+define+whether+parameters+or+local
variables+(or+both)+are+to+be+reported.|4646777|这可能只会使final成为可以安全的变量，但您试图发现的变量将仍然是非final的。尽管如此，这仍然是一种发现它们的方法。|4646778|entityMap^0|0|0|0|0|8|0|0|0|D|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|11|8|@$H|12|I|13|J|K]]|9|@]|A|$]]|$1|L|3|M|5|N|7|14|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|15|8|@$H|16|I|17|J|K]]|9|@]|A|$]]|$1|S|3|T|5|N|7|18|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

As Peter Lawrey suggests, IntelliJ does that.

Analyze -> Inspect code -> custom profile

There, in the "Code style issues" section, you have:

Field may be final

<pre><code>This inspection reports any fields which may safely be made final. A static field may 
be final if it is initialized in its declaration or in one static class initializer, but 
not both. A non-static field may be final if it is initialized in its declaration or in 
one non-static class initializer or in all constructors.
Powered by InspectionGadgets
</code></pre>

Local variable or parameter can be final

<pre><code>This inspection reports parameters or local variables, found in the specified inspection
scope, that may have a final modifier added.

Use check boxes in the inspection options below, to define whether parameters or local
variables (or both) are to be reported.
</code></pre>

That will propably only make final the variable that can safely be so but the ones that you're trying to spot will remain non-final. Still, it's a way to spot them.

I'm looking around for a way to perform batch refactoring on a complete Java application. In this namely make method arguments final where it's not the case yet.

Does somebody in here knows about such a tool ? Or something that parses Java source and that can be extended with such changes.

Batch refactoring to make Java method arguments final

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在寻找一种在完整的Java应用程序上执行批处理重构的方法。这就是说，在还不是这样的情况下，将方法参数设为final。这里有人知道这样的工具吗？或者解析Java源代码并可以通过这样的更改进行扩展的东西。

问批处理重构以使Java方法参数成为最终参数
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问批处理重构以使Java方法参数成为最终参数EN