Skip to content

Maven Central: com.pointbluetech coordinates, flattened pom, bin/publish-central - #129

Merged
jcombs-pointblue merged 1 commit into
masterfrom
maven-central
Nov 11, 2026
Merged

jcombs-pointblue merged 1 commit into
masterfrom
maven-central

Conversation

@jcombs-pointblue

Copy link
Copy Markdown
Contributor

Part of moving the Point Blue libraries to Maven Central under the verified namespace com.pointbluetech. Companion PRs are in DirXMLTraceViewer, DirXMLSimulator, directory-console and DirXMLDevWeb.

  • Coordinates: com.pointbluetech.dirxml:dirxml-dev, which depends on com.pointbluetech.dirxml:dirxml-simulator. Java packages don't change.
    • bin/idm, idm.cmd, require-engine.sh and doctor look for the simulator under the new path. doctor reads a simulator jar's version under either groupId (new tests).
    • After updating, run bin/install-deps, which installs the pinned 1.8.0 under the new groupId.
  • Flattened pom: what gets installed and published has no profiles, so it names no engine jar and no systemPath.
  • bin/publish-central: builds the central profile (sources, javadoc, gpg signatures). If any file in the bundle names something on the publish blocklist, it refuses; otherwise it uploads that same bundle to the Central Portal. The blocklist is ~/.config/pointblue/publish-blocklist, outside every repo, and matches whole words; the token comes from the Keychain.
  • bin/install-deps: takes each groupId from the pinning pom, and skips versions that are on Central.
  • install.md: §2.0 now has dirxml-dev before console-auth, which builds on it. New §2.0.1 covers Maven Central.
  • Client name removed: the blocklist check found a client name in ApplicationType's javadoc and in designer-new-project.md. It's gone from both.

Tested:

  • full mvn install and doctor OK;
  • a scratch 0.70.0 bundle signed with a throwaway key passes the check, and its pom names only postgresql, jldap and trace-core;
  • a word on the list refuses the bundle, and a missing list stops the publish.

🤖 Generated with Claude Code

…central

- groupId com.pointblue.dirxml -> com.pointbluetech.dirxml (the verified
  Central namespace), for dirxml-dev and the simulator it depends on. Java
  packages unchanged. Launchers, require-engine.sh and doctor look for the
  simulator under the new path; doctor reads a simulator jar's version
  under either groupId. bin/install-deps installs the pinned 1.8.0 there.
- flatten-maven-plugin: the installed/published pom has no profiles, so no
  engine jar and no systemPath.
- url, organization, developers, scm; a `central` profile (sources,
  javadoc, gpg, bundle built but not uploaded).
- bin/publish-central: builds the bundle, refuses it if any file names
  something on the publish blocklist (outside every repo), uploads that
  same bundle to the Central Portal (token from the Keychain).
- bin/install-deps: groupId from the pinning pom; skips versions on Central.
- install.md: dirxml-dev before console-auth (which builds on it); §2.0.1.
- A client name in ApplicationType's javadoc and designer-new-project.md,
  found by the blocklist check, is replaced.

Full mvn install passes; doctor OK. A scratch 0.70.0 bundle: signed, pom
names only postgresql, jldap, trace-core (and junit, test).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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