maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] (MECLIPSE-339) Add facet version configuration parameters
Date Tue, 25 Nov 2014 20:31:48 GMT


Michael Osipov closed MECLIPSE-339.

    Resolution: Won't Fix

Please refer to
if you're wondering why this issue was closed out.

> Add facet version configuration parameters
> ------------------------------------------
>                 Key: MECLIPSE-339
>                 URL:
>             Project: Maven Eclipse Plugin
>          Issue Type: Bug
>          Components: WTP support
>    Affects Versions: 2.4
>            Reporter: Shelley Baker
> The maven-eclipse-plugin uses the declared dependencies within the POM to determine the
facet versions in an EAR project, however, there may be a better approach.
> The JEE jar is rarely, if ever, actually required by the EAR since it is provided by
the container.  Requiring an unnecessary dependency to be configured for the project, only
to satisfy the maven-eclipse-plugin's configuration seems to violate Maven's principle of
separation of concerns.  (Further, due to licensing, the j2ee jars are not available in the
central repository, so an install of this jar may be required just to allow for successful
execution of the maven-eclipse-plugin.)  If these jars are already declared in the POM, it
makes sense to take advantage of them (to minimize configuration), however, in most cases,
when the JEE jar is not a true dependency, it seems like an invalid workaround for determining
the project facets in an EAR.
> Adding an "earVersion" configuration parameter, or simply allowing project facets to
be configured (overridden) in configuration might be a better approach.  (Currently, the maven-eclipse-plugin
allows "additionalProjectFacets" but does not allow the versions to be overridden.)

This message was sent by Atlassian JIRA

View raw message