[#MNGECLIPSE-171] For projects of type 'pom': Not always add Java nature when enabling Maven for the project

Maven Integration for Eclipse

For projects of type 'pom': Not always add Java nature when enabling Maven for the project

Created: 01/Aug/06 02:00 AM Updated: 01/Aug/06 10:48 AM

Component/s:

Dependency Resolver

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Description

« Hide

Linked to Issue: http://jira.codehaus.org/browse/MNGECLIPSE-53

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?

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Eugene Kuleshov - 01/Aug/06 10:48 AM

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.