Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Import order in referenced Libraries for unmanaged projects

Open
#1,023 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, typescript, vscode
Domain
build-system, tooling

Research direction

Start with the unmanaged-project setting in settings.json under java.project.referencedLibraries and compare its behavior with the ordering described for the Eclipse .classpath. Trace how referenced libraries are processed, then verify that the configured order determines which conflicting library version is used.

Written by the indexing model from the issue text.

Description

ai-triaged enhancement feature-request

Suggestion

When importing libraries in settings.json in "java.project.referencedLibraries" on a unmanaged project the order in which we import is not taken into account if there are conflicts between libraries.

Use Cases

I have a project that comes from Eclipse where the order of the entry on the .classpath is important, it will always take the first of the list in case of multiple occurence. I removed the classpath to be able to add libraries manually so it's now a unmanaged project and not an eclipse project anymore.

Examples

In my project i have many jars and some 3rd party libraries that have jars inside of them aswell, and there is some overlap between the ones i use and the ones these 3rd party libraries use, and these are not always the same version as the one i use.
So i have many errors in my project due to the fact that it takes the wrong version of the library and some function changed or does not exist anymore.

Thanks for reading me !

Dominant language
TypeScript
Stars
352
Forks
166
Avg merge
17h 47m
Merged PRs (30d)
32

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-java-pack

All issues in microsoft/vscode-java-pack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.