Skip to content

Can pick wrong ClassPathResolver #456

Open
@halfninja

Description

@halfninja

I've got a Gradle project whose build plan is defined by Bamboo Specs, which means there is a file called bamboo-specs/pom.xml in the project. This causes the server to use the MavenClassPathResolver, which is no good for building the actual app. If I rename pom.xml and restart the language server it picks the Gradle resolver and things work fine.

I'm not sure what the best way is to get around this - maybe rather than picking the first one, collect them all and prioritise based on which is highest up in the directory structure?

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependency resolutionRelated to the project dependency/standard library resolver

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions