Java EE 6的Maven与Eclipse项目构面 [英] Maven vs. Eclipse Project Facets for Java EE 6

问题描述

我已经使用这些原型在Eclipse中创建了Maven项目：

• ejb-javaee6


• webapp-javaee6

项目创建时没有方面。

将这样的Maven项目转换成分面形式是否有意义？

哪些方面将有所帮助，哪些方面可能会导致Maven的麻烦项目？

具体来说：以下任何项目方面是否与Maven的责任相冲突？

• Java


• JavaScript


• EJB模块


• 动态Web模块


• GlassFish部署描述符文件


• JavaServer Faces

我的印象是，将Maven项目转换为分面形式将意味着混合两个世界。因此，我倾向于不允许任何项目方面。

但是我在哪里工作，我们有一些面向Maven项目的例子，我想知道是否可能（风险 -

解决方案

Eclipse facet和maven原型是正交的 - 即它们对彼此没有影响，或而不是彼此的知识。您可以安全地添加方面，如果它将有助于您的eclipse工作。

I have created Maven projects inside Eclipse with these archetypes:

• ejb-javaee6
• webapp-javaee6

The projects were created without facets.

Does it make sense to convert such Maven projects into faceted form?

Which facets would be helpful and which ones could cause trouble for a Maven project?

Specifically: Would any of the following project facets be in conflict with something that is in the responsibility of Maven?

• Java
• JavaScript
• EJB Module
• Dynamic Web Module
• GlassFish Deployment Descriptors Files
• JavaServer Faces

I have the impression that converting a Maven project to faceted form would mean mixing two worlds. Therefore I tend to NOT enable ANY project facets.

But where I work we have examples of Maven projects that are in faceted form and I was wondering whether there might be (risk-free) benefits to it.

解决方案

Eclipse facets and maven archetypes are orthogonal - i.e. they have no influence on each other, or rather no knowledge of each other. You can safely add the facets if it will facilitate your work with eclipse.

这篇关于Java EE 6的Maven与Eclipse项目构面的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！