Add standalone Codename One Settings editor#5359
Open
shai-almog wants to merge 3 commits into
Open
Conversation
Collaborator
Author
|
Compared 144 screenshots: 144 matched. Native Android coverage
✅ Native Android screenshot tests passed. Native Android coverage
Benchmark ResultsDetailed Performance Metrics
|
Contributor
✅ Continuous Quality ReportTest & Coverage
Static Analysis
Generated automatically by the PR CI workflow. |
Collaborator
Author
Collaborator
Author
Apple Watch (watchOS / Core Graphics)Compared 216 screenshots: 215 matched, 1 updated. |
Collaborator
Author
|
Compared 142 screenshots: 142 matched. Benchmark Results
Detailed Performance Metrics
|
Collaborator
Author
|
Compared 139 screenshots: 139 matched. |
Collaborator
Author
|
Compared 143 screenshots: 143 matched. Benchmark Results
Build and Run Timing
Detailed Performance Metrics
|
Collaborator
Author
|
Compared 137 screenshots: 137 matched. Benchmark Results
Build and Run Timing
Detailed Performance Metrics
|
Contributor
Cloudflare Preview
|
4058983 to
781c897
Compare
Contributor
|
Developer Guide build artifacts are available for download from this workflow run:
Developer Guide quality checks: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
















Summary
scripts/settingscn1:settingsresolve and launchcom.codenameone:codenameone-settingsfrom Maven instead of the legacy GUI Builder jarmvn cn1:settings, document the replacement workflows, and replace legacy Control Center screenshotsDetails
The existing
cn1:settingsgoal launched the Settings UI embedded inguibuilder.jar. This introduces a separately versioned Maven artifact, binds it to the current CN1 project, and supplies a dedicated JavaSE launcher with native desktop identity, input, menu, icon, and About handling.The Settings UI includes structured basic settings and build-hint editing, live/bundled extension browsing, Maven and legacy cn1lib install/uninstall, light/dark themes, focus/caret behavior, and compatibility warnings. Bundled compatibility metadata is retained when the live catalog refresh omits it, so outdated entries such as Admob Fullscreen Ads still warn before installation.
The release workflow deploys the Settings reactor to Maven Central after the core release.
maven/update-version.shupdates the Settings parent/common/javase versions and CN1/plugin properties so release builds do not remain-SNAPSHOTand target the wrong repository.The developer guide now treats Settings as a standalone Maven tool, directs signing to the Certificate Wizard and build monitoring to the website, and uses current Basic, Build Hints, and Extensions screenshots.
Validation
mvn -Dmaven.repo.local=/tmp/cn1-local-repo -Pexecutable-jar -pl javase -am clean package -Dcodename1.platform=javase- 25 tests passedmvn -Dmaven.repo.local=/tmp/cn1-local-repo -pl codenameone-maven-plugin test- 215 tests passed, 1 skipped