Preparation work for following feature work

[Col-E]

Changes:

• Migrated dependency and plugin declarations to pull from libs.versions.toml
• Enabled build caching
• Broke up the single module setup into multiple modules
  • Updated gradle build files to retain build/staging-repo output for JReleaser while pulling from child modules
  • The demos module is configured to skip publishing, but any following module such as for work regarding Persistence for docking component layouts #13 will be automatically included
• Bumped Gradle to 9.4.1
• Bumped Java target to 21, removing the downgrader plugin targeting 17
• Bumped JavaFX to 21

Addresses:

• Use JSpecify Annotations for Nullability #19 - JSpecify usage
• Avoid Publishing Fat/Uber/Shaded JARs #20 - Downgrader usage concern
• Proposal: Update java version and remove donwgrader #22 - Target Java version, and downgrader usage concern
• Proposal: Update JavaFX to 21 #23 - Target JavaFX version
• Converting the project to a multi-module project #25 (Just the aspect of the title, not anything regarding the proposed module structure, this will facilitate that work)
• Define coding style and conventions #26 - Provide auto-formatter configs

[github-actions]

Unit Test results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 3eddb95. ± Comparison against base commit 2b02b88.

♻️ This comment has been updated with latest results.

[philliplbryant]

To keep commits small and focused on a single change, can you allow/enable the creation of sub-issues to be added to parent issues?

I'm currently envisioning incrementally integrating larger features like #13 (parent issue) using sub-issues such as

• Converting the project to a multi-module project #25
• Add persistence modules (new sub-issue)
• Convert Gradle from Kotlin DSL to Groovy DSL (new sub-issue)

[Col-E]

I dont see anything in the project settings page regarding sub-issues. Seems to be a preview feature, and I dont see it in the preview feature dashboard either.

[philliplbryant]

I dont see anything in the project settings page regarding sub-issues. Seems to be a preview feature, and I dont see it in the preview feature dashboard either.

If you're interested in enabling sub-issues, go to the repository main page → Settings → under Features make sure Issues is selected. To create a sub-issue, open the parent issue. At the bottom of the issue description click Create sub-issue.

[philliplbryant]

Gradle recommends using Convention Plugins via an included build instead of allprojects or subprojects.

[philliplbryant]

Approved (as if you need my approval ;0) with changes suggested.

[Col-E]

If you're interested in enabling sub-issues, go to the repository main page → Settings → under Features make sure Issues is selected. To create a sub-issue, open the parent issue. At the bottom of the issue description click Create sub-issue.

Issues are active, you wouldn't be able to make anything otherwise 😂 - And no sub-issue button/link appears on any issue under Bento. Checked that too earlier. Here's the options listed:

[philliplbryant]

Issues are active, you wouldn't be able to make anything otherwise 😂 - And no sub-issue button/link appears on any issue under Bento. Checked that too earlier. Here's the options listed:

I didn't pick the UI component names. I didn't see the checkbox initially, but it's there, it's not checked by default, and it's titled Issues.

Maybe it would be better for me to wait until you complete this preparation issue, create a different pull request with the persistence modules, and you can decide whether or not you want them. If you don't, that's fine. We can always maintain the the libraries separately.

[Col-E]

Its been checked by default for every repo I've ever created 🤔

[ianbrandt]

Its been checked by default for every repo I've ever created 🤔

This may be a permissions rather than an enablement issue: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues.

Who can use this feature?
People with at least triage permissions for a repository can add sub-issues.

[philliplbryant]

It wasn't intuitive to find, but it did the trick.

Again, if you want me to post the persistence work that I've done, I can do so when and if you're ready. I think it would be best for me to hold off on any further comments/issues until then.

[Col-E]

People with at least triage permissions for a repository can add sub-issues.

>https://docs.github.com/en/organizations

Ooooooh this is a thing that only affects organization projects. Ok thats why they don't show up here.

[Col-E]

Or... not? Have I really just glossed over this button for the past year or so that sub-issues have been supported for? Maybe I really do need my eyes checked.

[ianbrandt]

Or... not? Have I really just glossed over this button for the past year or so that sub-issues have been supported for? Maybe I really do need my eyes checked.

Looking at other personal account repos, I'm only seeing the "Create sub-issue" button on issues when I have the Collaborator role for the repo. I'm guessing for this feature the equivalent of having triage permission for an org repo is having the Collaborator role for a personal repo. That may be why you can see the button as an Owner of this repo, and @philliplbryant can't having not been added as a Collaborator. This action isn't explicitly called out in the docs, but it seems to align with the categories of actions a Collaborator can perform.

[Col-E]

Going to merge and handle using convention plugins as following cleanup. Everything else is in, and seems to be working as intended.