Install dependencies using settings not working

[Eric-Chomba]

Adding dependencies using settings is not working. E.g. trying to install JSON dependencies shows what seems like a progress bar in the middle, freezes settings & dependency is not installed in common/pom.xml

I tried in Intellij & Netbeans projects generated using initializr.

Codename One version: 7.0.274.

OS: Linux Ubuntu.

How can dependencies be added successfully using settings?

[shai-almog]

I see a problem. We'll fix that, but because it's in the settings it will need to wait for 7.0.276.

Which cn1lib here do you need though?

Most of the ones listed are probably out of date by now and not really needed.

[Eric-Chomba]

I am using these dependencies

• BouncyCastle
• JSON
• FileChooser
• JailbreakDetect
• Connectivity
• PhotoCropper
• QRScanner

[shai-almog]

Most of these now have alternatives in the Codename One core, so you can remove several dependencies after migrating the corresponding calls:

• BouncyCastle: The core now includes Cipher for AES/RSA encryption, Hash, Hmac, and Signature. Which BouncyCastle functionality are you using? These cover common needs, but aren't a replacement for every algorithm and format BouncyCastle supports.
• JSON: Use JSONParser to read JSON and JSONWriter to generate it, including fluent object/array builders. There's also direct Java object mapping: annotate your classes with @Mapped, then use Mappers to serialize with Mappers.toJson(object) and deserialize with Mappers.fromJson(json, MyClass.class). The mappers are generated at build time, so you can work directly with typed Java objects instead of manually unpacking JSON fields.
• FileChooser: Core now has Display.openFileChooser(). It accepts file extensions or MIME types and returns the selected file's path through the callback. It uses native document pickers where available.
• JailbreakDetect: Use DeviceIntegrity, particularly isDeviceCompromised() and getCompromiseReasons(), for root/jailbreak and related checks. These report the result without terminating the app.
• Connectivity: NetworkManager now provides getCurrentNetworkType(), isConnected(), and addNetworkTypeListener(). A connected network interface doesn't guarantee your server is reachable; ping(url, timeoutMillis) provides an HTTP reachability check and must run off the EDT.
• QRScanner: Use com.codename1.ai.vision.CodeScanner. CodeScanner.scan() opens a camera scanning screen and returns the decoded result asynchronously. Check CodeScanner.isSupported() first. For scanning an existing image or building a custom scanning screen, see BarcodeScanner.
• PhotoCropper: This depends on the interaction you need. Image supports programmatic cropping with subImage() and centered cropping/resizing with fill(). Those don't replace an interactive crop screen where the user drags and adjusts the selection, so you may still need PhotoCropper for that.

While these migrations will require code changes and the current version of Codename One, they are still worth doing. They will move you towards currently supported APIs that the cn1libs can't keep up with.

[Eric-Chomba]

I'll update codes to use these new APIs. Thanks.

I'm using BouncyCastle to

• Encrypt & decrypt large data transmitted between app & server using AES. I'll update this to use Cipher in the core.
• Encrypt app storage using EncryptedStorage.install("Password"). This doesn't seem to be in the core.

[Eric-Chomba]

In version 7.0.276 only FileChooser & QRScanner dependencies are installed successfully, other dependencies still fails.

[shai-almog]

You’re right about EncryptedStorage.install("Password"): that still comes from the BouncyCastle cn1lib. Keep that dependency for your existing encrypted storage. Core SecureStorage serves a different purpose and isn’t a drop-in replacement.

For the installation problem if it still isn't working try bypassing Settings:

1. Download BouncyCastleCN1Lib.cn1lib from our official library repository.
2. From your project’s common directory, run:

mvn cn1:install-cn1lib -Dfile=/absolute/path/to/BouncyCastleCN1Lib.cn1lib

This is the Maven installation step that creates the library wrapper and adds the dependency to common/pom.xml. Reload the Maven project in your IDE afterward.

The earlier fix corrected the download URL, but your report shows we still have an installation problem to investigate. Please share the error output from launching Settings with mvn cn1:settings and attempting one failed install. That will help distinguish a download failure from the Maven integration issue.