Skip to content

Simplify Kernel metadata loading approach #83

@andrus

Description

@andrus

Currently, we have multiple disparate metadata sources:

  1. jjava-kernel-metadata.json with variables substituted during build by Maven and packaged in the jar. It is redundant. Using Maven module name as the "project" name is not we want and version can be taken from Maven metadata (see below).
  2. kernel-metadata.json is not something known or required by Jupyter, is not a part of our distro, and is fully external the project. I think it came from the Kaggle world, and the assumption of its presence on the Kernel classpath is entirely unwarranted. Let's remove this mechanism completely.

Instead, let's prvide the kernel name in the "main" menthod starting the kernel, and take version from Maven the metadata in the jar (e.g., META-INF/maven/org.dflib.jjava/jjava/pom.properties)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions