Maven 多模块和 EAR 可以很好地协同工作吗？
今天，我一直在研究 Maven 多模块和 EAR 项目，它们看起来非常相似，因为两者似乎都定义了其他项目集合的集合 - 几乎看起来 EAR 项目应该只是多模块项目。
我是不是误会了什么？或者这些类型的项目可以一起工作吗？
以下是帕斯卡的回答： 更新以澄清问题，如果不容易理解，希望这会有所帮助；抱歉，它的措辞可能不太好，耳朵的东西对我来说有点新鲜……
所以假设我有两个项目，一个产生一场战争，另一个产生一个实用程序罐子。战争取决于jar，我需要将它们打包到耳朵中进行部署。我应该使用 pom 打包类型的项目吗？我想我必须在某个地方使用带有 Ear 包装类型的项目来生成最终的工件，所以我最好只使用带有 Ear 包装的项目，还是同时带有 pom 和 Ear 的项目？如果两者都有，怎么办？
Today, I've been looking at Maven Multi-Module and EAR projects and they seem quite similar in that both seem to define an assembly of a collection of other projects - it almost seems like an EAR project should just be an alternate packaging for a multi-module project.
Have I misunderstood something? Or do these types of project work together?
Following Pascal's answer:
Updated to clarify the question, hopefully that will help if it's not easy to understand; sorry it's maybe not phrased very well, the ear stuff is kinda new to me...
So say I have two projects, one producing a war and the other a utility jar. The war depends on the jar and I need to package them up into an ear for deployment. Should I use a project with a pom packaging type? I guess I have to use a project with an ear packaging type somewhere to produce the final artifact, so am I best using just a project with ear packaging, or projects with both pom and ear? If both, how?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
EAR 项目作为更大的聚合项目的一部分工作得很好。在这些情况下，当您不希望 EAR 成为一个单独的项目时；您始终可以通过程序集创建文件。
这种方法在某些情况下是有意义的。通常，您必须创建 EAR 的多个版本，或者您想要创建和部署大型 EAR 文件，但创建后无需保留工件。
我已经使用这种方法来处理要求所有可部署文件都是 EAR 文件的公司标准，即使应用程序是单个 WAR 文件也是如此。程序集可以使用其单个 WAR 文件和部署描述符创建 EAR。
EAR projects work just fine as part of a larger aggregated project. In those cases when you do not want to have the EAR be a separate project; you could always create the file via an assembly.
This approach makes sense in some cases. Usually where you have to create multiple versions of the EAR or when you would like to create the deploy a large EAR file but have no need to keep the artifact once created.
I've used this approach to deal with a corporate standard that requires all deployable to be EAR files, even when the app is a single WAR file. An assembly can create the EAR with its single WAR file and deployment descriptors.
我不确定我是否理解这个问题，但我很想回答它们可以一起工作：
pom包装（并且只有pom模块可以有嵌套项目）。ear包装的模块（并且具有特定的 绑定）并且可以是多模块项目的一部分。两者都有不同的目的。但他们一起工作。
I'm not sure I understood the question but I'm tempted to answer that they work together:
pompackaging (and onlypommodules can have nested projects).earpackaging (and has specific bindings) and can be part of a multi-module project.Both have different purposes. But they work together.