Annotate modules list with plugin name, origin, and status - #342
Merged
Merged
Conversation
Each <module> entry in the root pom.xml now records the plugin's own display name, whether it's tracked via a contributor fork or an adopted branch, and its build status (active, or disabled with a reason). This makes the <modules> list a self-contained source of truth for which plugins are managed here and where their code actually comes from — see CONTRIBUTING.md's new "Documenting a plugin in master-forge's <modules> list" section for the convention. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Sep 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<module>entry with three comments —name(the plugin's own display name),origin(fork (owner/repo)orbranch (name)), andstatus(activeordisabled — <reason>) — per the convention documented in Document module-list annotation convention in CONTRIBUTING.md #341.SemanticWebImport,MapOfCountries,ExcelCsvImporter,dbscan,KleinbergGenerator: no PR could be traced (pre-dates PR-linked history) — origin recorded asunknown (git author: ...).SemanticWebImport,ScriptingPlugin,TwitterStreamingImporterV2,AgensGraphPlugin,image-preview,Neo4jPlugin: were already commented out with no reason given — markeddisabled — reason not recordedrather than inventing one.GroupPartition(s-puig),ForceAtlas3D(seinecle),Neo4jPlugin(sim51): source fork repos are confirmed deleted on GitHub — origin still recorded from PR history, flagged "repo now deleted".BlueskyGephi: active, but carries a pre-existing caveat comment ("needs to not create a project at start") from when it was briefly disabled for that reason and later re-enabled without a confirmed fix — preserved as a status caveat rather than dropped.Test plan
xmllint --noout pom.xmlpasses (well-formed XML).<module>ordering, and disabled/active state are unchanged from before.origin/nameagainst your own knowledge of the plugin, since a chunk of this was reconstructed from years-old commit/PR history.