Skip to content

review cases where Java/Scala packages are split across 2 or more jars #2113

@pjfanning

Description

@pjfanning

Java Modules (JPMs) discourage having packages where classes appear in different jars. It is a security risk to have the possibility of rogue jar including classes that hide classes in a well known jar.

cluster-typed and distributed-data share the package

  • org.apache.pekko.cluster.ddata
    • we may be ok as is because the cluster-typed packages are all grouped under org.apache.pekko.cluster.ddata.typed and there are packages in distributed-data that appear under org.apache.pekko.cluster.ddata.typed or packages that are grouped under it

There may are more instances. This is just one that I spotted today.

Related:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions