在单个Maven模块生成源中以编程方式禁用Eclipse警告？
我有一个多模型Maven项目，其中一个模块负责在我们的OpenApi.yaml文件上调用OpenApi Generator在项目的其余部分。这效果很好。
不幸的是，这些产生的来源在进口Maven项目后引发了2022 - 03年Eclipse的许多警告。因此，我想知道是否只能让M2E调整此模块的一些编译器设置，导入项目时，或者我唯一的选择是在Eclipse中设置此设置，然后仔细提交所得的配置文件？
我们的目标是尽可能接近“纯Maven”解决方案。可以做到吗？
I have a multi-module Maven project, in which one module is responsible for invoking OpenAPI generator on our openapi.yaml file resulting in a lot of Java sources under target/ which is then compiled into an artifact used in the rest of the project. This works well.
Unfortunately these generated sources trigger quite a few warnings in Eclipse 2022-03 after importing the Maven project. I would therefore like to know if it is possible to have m2e adjust a few compiler settings for this module only, when importing the project, or if my only option is to set this in Eclipse and then carefully commit the resulting configuration files?
Our goal is to have as near a "pure Maven" solution as possible. Can this be done?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论