The core profile now boots a seeded QQQ reference app with H2, SQLite, local filesystem storage, the Next dashboard, mock demo identities, and an embedded Artemis broker. Order inserts and updates publish to orderEvents and trigger syncOrder. The standalone jar binds to loopback by default because core uses fixed demo identities.
Validation: mvn -o -pl qqq-all-app -am verify -q passed. Surefire covers backend queries and the ESB round trip; Failsafe starts the shaded jar, checks loopback binding and health, and queries seeded customer data over HTTP. Independent review passed after the bind and jar-test fixes.
Closes #4.
The `core` profile now boots a seeded QQQ reference app with H2, SQLite, local filesystem storage, the Next dashboard, mock demo identities, and an embedded Artemis broker. Order inserts and updates publish to `orderEvents` and trigger `syncOrder`. The standalone jar binds to loopback by default because core uses fixed demo identities.
Validation: `mvn -o -pl qqq-all-app -am verify -q` passed. Surefire covers backend queries and the ESB round trip; Failsafe starts the shaded jar, checks loopback binding and health, and queries seeded customer data over HTTP. Independent review passed after the bind and jar-test fixes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #4.
The
coreprofile now boots a seeded QQQ reference app with H2, SQLite, local filesystem storage, the Next dashboard, mock demo identities, and an embedded Artemis broker. Order inserts and updates publish toorderEventsand triggersyncOrder. The standalone jar binds to loopback by default because core uses fixed demo identities.Validation:
mvn -o -pl qqq-all-app -am verify -qpassed. Surefire covers backend queries and the ESB round trip; Failsafe starts the shaded jar, checks loopback binding and health, and queries seeded customer data over HTTP. Independent review passed after the bind and jar-test fixes.