Skip to content

Add support for packages that aren't in Maven #73

@milesziemer

Description

@milesziemer

This is related to #67 , but would be a more comprehensive fix. If your model uses some packages that aren't available in Maven, builds can be successful but the language server will not be able to resolve the dependencies and provide its features with any traits or shapes you use from those dependencies. One idea on how we might be able to do this is if these dependencies are jars somewhere locally, we could provide these paths to the language server directly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions