blocks|key|1600993|text|为此，您可以使用WildFly+16+Bill+of+Materials+(BOM)。我相信您很清楚Maven为POM类型的工件提供的导入功能。如果不是这样，请将这些行添加到Maven+pom.xml中|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1600994|<dependencyManagement>
++<dependencies>
++++++<dependency>
++++++++<groupId>org.wildfly.bom</groupId>
++++++++<artifactId>wildfly-javaee8</artifactId>
++++++++<version>16.0.0.Final</version>
++++++++<type>pom</type>
++++++++<scope>import</scope>
++++</dependency>
++</dependencies>
</dependencyManagement>|code-block|syntax|javascript|1600995|它使您能够引用大多数WildFly的工件(或者至少是相关的工件)以及Java+EE+8规范工件。下面是一个例子：|1600996|<dependencies>
++<dependency>
++++<groupId>org.hibernate</groupId>
++++<artifactId>hibernate-entitymanager</artifactId>
++++<scope>provided</scope>
++</dependency>
++<dependency>
++++<groupId>org.jboss.spec.javax.servlet</groupId>
++++<artifactId>jboss-servlet-api_4.0_spec</artifactId>
++++<scope>provided</scope>
++</dependency>
</dependencies>
|1600997|不过，您仍然需要列出所需的所有依赖项。如果您有其他依赖项(不是由WildFly提供的)，则应该将它们打包到WAR或EAR中。这样你就不会有任何冲突。|1600998|哦，还有一件事，因为您提到了几个特定于WildFly的依赖项(例如，Weld和Hibernate)：尽可能坚持使用Java。如果需要，它使您能够更快地将应用程序移植到其他应用程序服务器。|1600999|entityMap|0|LINK|mutability|MUTABLE|url|https://search.maven.org/artifact/org.wildfly.bom/wildfly-javaee8/16.0.0.Final/pom^0|2L|7|8|Y|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|17|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|19|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1A|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

You can use the <a href="https://search.maven.org/artifact/org.wildfly.bom/wildfly-javaee8/16.0.0.Final/pom" rel="nofollow noreferrer">WildFly 16 Bill of Materials (BOM)</a> for that. I'm sure you are well aware of Maven's import feature for artifacts of type POM. Just in case you are not, add these lines to your Maven <code>pom.xml</code>:

<pre><code>&lt;dependencyManagement&gt;
 &lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.wildfly.bom&lt;/groupId&gt;
 &lt;artifactId&gt;wildfly-javaee8&lt;/artifactId&gt;
 &lt;version&gt;16.0.0.Final&lt;/version&gt;
 &lt;type&gt;pom&lt;/type&gt;
 &lt;scope&gt;import&lt;/scope&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
&lt;/dependencyManagement&gt;
</code></pre>

It enables you to reference most of WildFly's artifacts (or at least the relevant ones) as well as the Java EE 8 specification artifacts. Here's an example:

<pre><code>&lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.hibernate&lt;/groupId&gt;
 &lt;artifactId&gt;hibernate-entitymanager&lt;/artifactId&gt;
 &lt;scope&gt;provided&lt;/scope&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.jboss.spec.javax.servlet&lt;/groupId&gt;
 &lt;artifactId&gt;jboss-servlet-api_4.0_spec&lt;/artifactId&gt;
 &lt;scope&gt;provided&lt;/scope&gt;
 &lt;/dependency&gt;
&lt;/dependencies&gt;
&lt;!-- And so on... --&gt;
</code></pre>

You still need to list all the dependencies you require though. If you have additional dependencies (not provided by WildFly), you should package them in your WAR or EAR. This way you shouldn't get any conflicts.

Oh, and one more thing, because you mentioned several dependencies, which are WildFly specific (e.g. Weld and Hibernate): Try sticking to Java EE APIs, where possible. It enables you to port your application to other application servers faster, if needed.

I am working on a Project that is deployed as .war WebApp on a single WildFly 16 instance. 

Using IntelliJ Idea UE with Maven as development environment, I ask myself how to reflect the classpath that the deployed app will see at runtime in the development classpath at development time. 

I have read about <a href="https://docs.wildfly.org/16/Developer_Guide.html#which-are-the-implicit-module-dependencies" rel="nofollow noreferrer">implicit dependencies</a> in the Developer Guide. 
So I conclude that the classpath of my deployment will contain the elements from the "Dependencies that are always added" column plus those that are added on trigger conditions (in my case these are Weld, Web, Hibernate, Resteasy, EJB3). 

How can I figure out what Maven artifacts I have to import so that my development classpath equals the runtime classpath of my WebApp?

I would like to solve dependency conflicts at development time, not at runtime.

WildFly App Dev: how to reflect the runtime classpath at development time?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在处理一个项目，该项目作为.war WebApp部署在单个WildFly 16实例上。使用IntelliJ Idea UE和Maven作为开发环境，我问自己如何在开发时在开发类路径中反映部署的应用程序将在运行时看到的类路径。我在“开发人员指南”中读到过有关的内容。因此，我得出结论，我的部署的类路径将包含"Depen...

WildFly应用程序开发人员:如何在开发时反映运行时类路径？-腾讯云开发者社区-腾讯云

问WildFly应用程序开发人员:如何在开发时反映运行时类路径？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WildFly应用程序开发人员:如何在开发时反映运行时类路径？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WildFly应用程序开发人员:如何在开发时反映运行时类路径？
EN