Skip to content

Support Maven/Gradle multi-module project structure #99

@mircealungu

Description

@mircealungu

Problem

ArchLens assumes a flat source layout where rootFolder points to a directory containing the source tree directly (e.g. src/ for Python, src/MyApp/ for C#).

Maven/Gradle projects have a very different structure:

project/
  module-a/src/main/java/org/example/modulea/...
  module-b/src/main/java/org/example/moduleb/...
  module-c/src/main/java/org/example/modulec/...

Setting rootFolder: "." doesn't work because the Java files are nested deep inside <module>/src/main/java/<package-path>/. The parser can't map the directory structure to Java packages.

Tested with

Apache Wayang — a multi-module Maven project. Even with the correct name (org.apache.wayang) and rootFolder: ".", the parser produces an empty diagram.

Suggestion

  • Recognize standard Maven/Gradle src/main/java layout and use that as the source root within each module
  • Or allow multiple rootFolder entries
  • Or auto-discover source roots by looking for pom.xml / build.gradle files

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions