Skip to content

Import Maven Projects with groupId + artifactId + version to avoid duplicate error on import #4552

Closed
eclipse-jdtls/eclipse.jdt.ls
#3948

Description

@FlyingSheepOnSailfish

The Problem

On importing Java projects we get errors like this:

23 Maven project(s) could not be imported due to duplicate groupId/artifactId. See the language server log for details.

We are using a multi-root workspace:

  • Each root folder imports a Java multi-project project from a seperate git local repo.
  • Each repo / folder is a set to a different release branch from the same git repo.

This means that each root folder contains substantially the same set of maven projects, with the same groupId(s) and artifactId(s), but with different version(s).

i.e. as indicated by the error, groupId + artifactId is duplicate / ambiguous,
but the combination groupId + artifactId + version is unique.
For our maven projects the property name is also unique.

Proposed Solution

It should be possible to configure which maven properties are used to import maven projects:
e.g. groupId + artifactId + version
or groupId + artifactId + name

Note the Eclipse IDE when properly configured supports our project structure. Eclipse is able make otherwise duplicate maven projects unique on import via the "Import Maven Projects / Advanced / Name Template" option.

Describe alternatives you've considered

We have seen the setting "maven.explorer.projectName": "${project.groupId}.${project.artifactId}-${project.version}", but that has no effect on project import.

How to Reproduce

The issue can be demonstrated with:

A trusted multi-root-workspace "foo" with two folders foo_one and foo_two imported:

workspace "foo"
├─foo_one
│ └── demo
│     └── pom.xml
└─foo_two
  └── demo
      └── pom.xml

foo_one is a maven project with this pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>foo.bar</groupId>
    <artifactId>demo</artifactId>
    <version>1.0</version>

    <properties>
        <maven.compiler.source>25</maven.compiler.source>
        <maven.compiler.target>25</maven.compiler.target>
    </properties>
</project>

foo_two is a maven project with this pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>foo.bar</groupId>
    <artifactId>demo</artifactId>
    <version>2.0</version>

    <properties>
        <maven.compiler.source>25</maven.compiler.source>
        <maven.compiler.target>25</maven.compiler.target>
    </properties>
</project>

The projects differ only in the version (1.0) vs (2.0)

My Setup
IBM Bob Version: 1.126.0+bob2.2.3
VSCode Version: 1.126.0
Bob Version: 2.2.3
Extension Pack for Java 0.31.2
Language Suppor for Java(TM) by RedHat pre-release 1.59.2026102008
Maven for Java 0.45.3
OS: Darwin arm64 27.0.0

The issue 2806 may be related

Activity

  1. changed the title [-]Import Maven Projects with groupId + artifactId + version to avoid duplicate error[/-] [+]Import Maven Projects with groupId + artifactId + version to avoid duplicate error on import[/+] on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions