Bump com.pi4j:pi4j-core from 1.4 to 2.6.0

[dependabot]

Bumps com.pi4j:pi4j-core from 1.4 to 2.6.0.

Release notes

Sourced from com.pi4j:pi4j-core's releases.

PWM and I2C Improvements

• New hardware PWM provider added to the GpioD plugin, see:
  • Blog: PWM Hardware Support on RPi5.
  • Documentation: I/O Examples: Pulse Width Modulation (PWM).
• Various improvements in the I2C implementation in both core and plugins, see:
  • Blog: Ongoing I2C Improvements.
• Dependency bumps in the pom file, see [pull request #337](Pi4J/pi4j-v2#337).
• New BoardInfo included to detect type of Raspberry Pi board, providing a lot of info about the board, SoC, pins, etc., see:
  • Documentation: Using Board Info.
  • Example implementation and visualization on api.pi4j.com.
• Fix for "IOBase constructor do not update the fields id, name & description".
  • [Issue #257](Pi4J/pi4j-v2#257): IOAlreadyExistsException when reopening Serial-connection.
  • [Issue #244](Pi4J/pi4j-v2#244): Multiple SPI throws IOAlreadyExistsException.
• Several code improvements and clean-up.

Thanks to contributions by @​fusetim, @​taartspi, @​eitch, @​fdelporte.

Make sure to also read the interviews with Robert von Burg and Tom Aarts.

All changes: Pi4J/pi4j-v2@2.5.1...2.6.0

Correct native code for GpioD

Sorry! Because of a configuration error, the wrong native code is included in 2.5.0 for the new GpioD Provider. But thanks to the lightning fast action of Robert von Burg we have a fixed version for you to enjoy :-)`

For all other info about the changes in 2.5, see the release notes of 2.5.0.

A lot of changes and... support for Raspberry Pi 5!

With over 100 commits from multiple branches, this is a major release with many improvements! With many thanks to the core team (Robert von Burg, Tom Aarts), and a major addition of Alexander Liggesmeyer, Pi4J is again lifted to a higher level!

Warning, the new GpioD Provider needs the latest Raspberry Pi OS version (Debian GNU/Linux 12 (bookworm))

Changes in 2.5.0

• A new GpioD Provider adds support for the Raspberry Pi 5.
  • Issues #321, #320, #317
  • This new GpioD provider interfaces directly with the Raspberry Pi's gpiochip device, located at /dev/gpiochip.... It leverages the native libgpiod library, which is developed as a part of the Linux kernel. Libgpiod is currently the recommended way to control GPIO pins. Therefore, using this provider is also recommended.
  • This new provider can be used without the need to start a Pi4J application with sudo, so also fixes #212 when you only need DigitalInput and/or DigitalOutput.
• Better handling of mock Plugins: Plugins can now define if they are mocks, and these are not auto-detected anymore. The default target for the Pi4J library is the Raspberry Pi, and thus auto-detecting mocks on the Pi, which are only for tests is counterintuitive.
• Extended Providers with a priority: this priority helps to determine which Provider should be loaded, when multiple Providers with the same IOType are being loaded by different plugins. This change enforces that a given IOType can only have one Provider loaded at runtime preventing errors when, for instance, two I2C providers are loaded at the same time, concurrently writing to the I2C bus.
• Fix for: LinuxFile reused scratch buffers ensuring size was usable. But the limit value cannot be modified so later usage failed as an intended overwrite. Pull request #331, commit ed208f2.
• Fix for: I2C interface should use a restart between the write and read operation. Pull request #333.
• Fix for: Shutting down pool executor too early. Commit 7909a2d.
• ProviderProxyHandler got removed, simplifying provider loading, thus no more reflection on the instances.
• You can now add and remove IO instances at runtime.
• You can now easily switch a GPIO from output to an input and vice versa, see issue #26, extending on the work by @​MEBoo, in pull request #1.
• A race condition got fixed in the default runtime registry.
• Proper life cycle management got added for of all threads in Pi4J.

All changes: Pi4J/pi4j-v2@2.4.0...2.5.0

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)