Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 357215

Summary:	Please allow artifactId to be separate from module name while creating a new maven module
Product:	z_Archived	Reporter:	Sahoo <sanjeeb.sahoo>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	igor, mkleint
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Sahoo

2011-09-09 07:22:39 EDT

Build Identifier: 20110615-0604

New Maven Module wizard automatically sets artifactId as module name. It does not even allow it to be changed which is bad, because the module name and artifactId are really independent of each other and have different functionalities. While the former is used as the directory name, the latter is used as in forming the maven coordinate. There are many projects (many in Apache land itself) which follow a hierarchical directory structure and artifact naming structure and m2e can't be used to create new modules in those projects. e.g., it is a common practice to set up a project like this:
a/          <-- artifactId=a
 b/         <-- artifactId=a.b
  c/        <-- artifactId=a.b.c
m2e can't handle this case.

Reproducible: Always

Comment 1 Milos Kleint

2011-09-09 07:24:18 EDT

you will get trouble down the road with releases and the scm plugin afaik when the artifactid differs from the folder name, that's why it's enforced.

Comment 2 Igor Fedorenko

2011-09-09 07:37:20 EDT

There are no plans to allow module name and artifactId differ in New Module wizard. Allow allowed by Maven, this considered a bad practice and many Maven plugins assume module directory name and atifactId match. If you want them different, you can always create module project manually.

Comment 3 Sahoo

2011-09-09 07:47:44 EDT

What is the harm in allowing user to override a best practice setting? As I said, I have seen plenty of very very advanced and popular apache projects which don't have artifactId == module name. That basically means there are a class of projects which do not suffer from the problems you foresee. So, why not allow them to make use of m2e? Conventions over configurations is good, but don't let that become a bottleneck. More over, instead of closing bugs like this, I suggest waiting for others to vote. If you tell me this was discussed earlier and a decision was reached, I will be happy to see that result.

Comment 4 Igor Fedorenko

2011-09-09 09:12:39 EDT

The wizard is a convenience, not something one has to use to create module projects. We won't complicate the UI and confuse the vast majority of m2e users for the benefit of the few who may have reasons to deviate from the convention.

Comment 5 Milos Kleint

2011-12-22 07:18:22 EST

+1 on igor's last command and closing the issue

Comment 6 Denis Roy

2021-04-19 13:24:22 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/