Part 12 of this project

Package

Package Tableforge with jpackage notes

Goal for this part

Package Tableforge with jpackage notes.

Treat 12-Package as the source of truth for this checkpoint. If your local tree drifted, re-clone that folder rather than mixing files from neighbors.

What you should already know

You do not need prior JavaFX experience for part 1. Later parts assume you finished the earlier snapshots on the same machine.

  • JDK 17+ and Maven are installed
  • You can run mvn from a terminal
  • You have a desktop session for the GUI window

Why JavaFX fits Tableforge

A teaching DBMS is a SQL workbench: connections, result grids, and scripts. JavaFX TableView plus JDBC keeps each piece visible.

Split the stage into schema tree, SQL editor, and results. Prepared statements belong in the data layer—not glued to button handlers forever.

Checkpoint

After you run the snapshot, you should recognize the behavior described in the goal—before you move on. If the window (or server) never appears, stop and fix the run steps.

Code shape

Snapshots stay small on purpose. Look for this kind of core call as you read the folder:

st.executeQuery("SELECT name FROM sqlite_master WHERE type='table'");

How to run it

Clone the teaching repo, open 12-Package, install what the README asks for, then run mvn javafx:run.

git clone https://github.com/michaeldunga1/fcc-javafx-dbms.git
cd fcc-javafx-dbms/12-Package
mvn -q -DskipTests package
mvn javafx:run

Common mistakes

  • Ignoring platform-specific install notes in the snapshot README
  • Packaging before the final snapshot still runs cleanly
  • Bundling a development database full of test junk
  • Shipping without a short README for end users