Skip to content
akuhtzPublic

About

Swing UI Enhacements

Resources

Contributing

Stars

3 stars

Watchers

1 watching

Forks

 
 

Latest commit

 

History

188 Commits

Folders and files

Repository files navigation

Build Status Maven Central

SwingBits is a collection of useful components and utilities for Java Swing Toolkit.

The documentation can be found in the Project Wiki.

 NOTE: The TaskDialog library is becoming a part of SwingBits starting with SwingBits v1.0 

Here are some of its features:

Table Filtering

Table Filtering

Task Dialogs

Nimbus LAF Task Dialog

Windows LAF Task Dialog

Task Dialog 3

Task Dialog 5

Windows LAF Exception Dialog

One-time setup

Copy the relevant bits from settings.xml.example into your own ~/.m2/settings.xml:

  • a <server id="sonatype-central-portal"> entry with your token as username/password, and njord.publisher / njord.releaseUrl configuration so Njord knows this server means "publish to Central Portal"
  • (optional) a <pluginGroup> entry so you can type mvn njord:... instead of the fully-qualified plugin coordinates

For the GPG passphrase, the recommended approach is to not put it in settings.xml at all — export it as an environment variable right before signing:

export MAVEN_GPG_PASSPHRASE="your-passphrase"

(settings.xml.example also shows the older <server id="gpg.passphrase"> convention, which still works but is discouraged since 3.2.x of the plugin.)

Build & test (no signing, no publishing)

mvn verify

The release profile (and therefore GPG signing) is not active by default, so this works without a GPG key present.

Stage, sign, and publish

  1. Locally stage the release (this creates a Njord "store"; the id before ::njord: is a throwaway value just to satisfy deploy-plugin syntax):

    mvn -Prelease deploy -DaltDeploymentRepository=id::njord:

    Because the release profile is active, maven-gpg-plugin signs the jar, sources jar, javadoc jar and POM during the verify phase, before Njord stages everything locally.

  2. List staged stores to get the store name:

    mvn njord:list
  3. Inspect what got staged (optional but recommended):

    mvn njord:list-content -Dnjord.store=release-xxx
  4. Validate the store against Central's requirements (optional but recommended — catches missing sources/javadoc/signatures/POM metadata before you publish):

    mvn njord:validate -Ddetails -Dnjord.store=release-xxx
  5. Publish to Central Portal:

    mvn njord:publish -Dnjord.store=release-xxx -Dnjord.publisher=sonatype-cp
  6. If publish succeeds, the store is dropped automatically and your release is now on Central Portal (check https://central.sonatype.com/publishing to confirm/finalize, depending on whether your namespace has automatic publishing enabled).

If you ever want to abandon a staged release instead of publishing it:

mvn njord:drop -Dnjord.store=release-xxx

Notes

  • Replace the placeholder groupId, url, scm, developers and licenses in pom.xml with real values — Central Portal validates that this metadata is present and rejects releases that lack it.
  • version.njord in pom.xml should be bumped to whatever the latest Njord release is at the time you use this.
  • Signing is scoped to the release profile so everyday mvn test / mvn install don't require a GPG key on every dev machine / CI job.

About

Swing UI Enhacements

Resources

Contributing

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages