maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Kuleshov (JIRA)" <>
Subject [jira] Closed: (MNGECLIPSE-171) For projects of type 'pom': Not always add Java nature when enabling Maven for the project
Date Tue, 01 Aug 2006 15:49:31 GMT
     [ ]

Eugene Kuleshov closed MNGECLIPSE-171.

    Resolution: Won't Fix

The only reason to enable maven nature is to make dynamic dependency resolution to work. So,
it really does not make any sense to have it without java nature. Besides, you don't have
to enable maven support and add maven nature if you don't need dynamic dependency resolution.

Also note, that pom packaging can be used in a root pom.xml and submodules may go into the
same Eclipse project (unless flat module layout is used). So, those modules will give java
source folders even if root module does not have any source folders. We already have update
source folders action that takes care of this.

> For projects of type 'pom':  Not always add Java nature when enabling Maven for the project
> -------------------------------------------------------------------------------------------
>                 Key: MNGECLIPSE-171
>                 URL:
>             Project: Maven 2.x Extension for Eclipse
>          Issue Type: Wish
>          Components: Dependency Resolver
>            Reporter: Marc Portier
>         Assigned To: Eugene Kuleshov
> Linked to Issue:
> It's  my feeling that adding the java-nature to in essence 'simple' projects of packaing-type
'pom' is not desirable since it will make eclipse go and look for java source-folders and
wrongly interpret module-directories and the nested src/main/java as package-names leading
to lists of errors about bad package names.
> I'm unsure if the goal of this plugin is ever to support these kind of pom-projects in
eclipse or not, for now the safe bet looks like trying to enable such a project of type 'pom'
should be disabled?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message