Skip to content

Document suite grouping in the modules-list convention - #343

Merged
mbastian merged 1 commit into
masterfrom
document-suite-modules-convention
Sep 20, 2026
Merged

mbastian merged 1 commit into
masterfrom
document-suite-modules-convention

Conversation

@mbastian

Copy link
Copy Markdown
Member

Summary

  • Follow-up to Document module-list annotation convention in CONTRIBUTING.md #341/Annotate modules list with plugin name, origin, and status #342: a plugin suite's modules (API/Impl/UI, or a bundled dependency like JettyWrapper) share one origin and one status, so they shouldn't repeat the same three-comment block per folder.
  • Adds a rule to precede the whole run of <module> lines with a single block, using the suite's main module for name — identified objectively as the one module in the group whose manifest.mf does not set AutoUpdate-Show-In-Client: false (the other modules mark themselves as implementation details hidden from Gephi's plugin manager).
  • Companion PR applying this to the two existing suites in master-forge's pom.xml (Graph Streaming, BoundingDiameters Suite).

Test plan

  • Docs-only change, no build impact.

A suite's modules share one origin and one status, so they don't need
the name/origin/status comment repeated per folder. Use the suite's
main module (the one not marked AutoUpdate-Show-In-Client: false) for
name, and group the whole run of <module> lines under one block.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@mbastian
mbastian merged commit fd72106 into master Sep 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant