Update Gradle dependency : Bump com.pi4j:pi4j-core from 1.4 to 3.0.2

[dependabot]

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

Release notes

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

3.0.2

• Board model can now be forced to allow the use of Pi4J on other/unrecognized boards. See Overriding the Detected Board for more info.
• BoardInfoHelper.usesRP1() has been improved as more boards use this RP1 (5, 500, Compute 5), and even more are expected in the future.
• [Issue #455](Pi4J/pi4j#455): GpioDDigitalInput may never start monitoring line events. Fixed by simplifying and improving the wait for the input listener loop to exit on shutdown.
• APIdia badge and link added to README.md
• [Pull request #461](Pi4J/pi4j#461): Removal in the core code of the SpiChipSelect to enforce a PiGpio limitation of the values 0, 1, or 2.

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

All changes: Pi4J/pi4j@3.0.1...3.0.2

3.0.1

This is the first release of Pi4J that requires Java runtime 21 or higher. Check the blog post Pi4J welcomes Java 21 to understand why we needed this change to prepare the project for the future...

Because of a last-minute change to improve the detection of Raspberry Pi 5, 500, and Compute 5, release 3.0.0 has been skipped.

• Bump the Java version to 21 and update many dependencies, such as the Maven plugin.
• Added JNA dependency (needed for Java 21).
• Added Maven wrapper.
• Improved lifecycle shutdown handling for registry elements: Updated the Lifecycle interface to clarify shutdown behavior and added tests to ensure proper element recreation after shutdown. These enhancements make the shutdown process more robust and intuitive.
• Issue #308: Remove serial support from Pi4J. All serial methods are marked as @Deprecated(forRemoval = true). We advise using jSerialComm for all serial communication.
• Pull request #438: Extra unit test for shutdown and re-creation of a DigitalInput.
• Issue #439: Allow Specifying GPIO Chip for GpioDContext. For more info on how to use, see Specifying the GPIO Chip.
• Pull request #449: Fixes a minor bug in DigitalOutput where pulseAsync ignored the given state and always pulsed high.
• Pull request #452: PWM linuxfs failed if the first interface call was off().
• Pull request #453 for issue #296: Generic BoardModels (with and without RP1) have been added, with a new method BoardInfoHelper.current().setBoardModel(BoardModel.GENERIC); to make it possible to use Pi4J on other types of boards, see Overriding the Detected Board. The goal of the Pi4J project is still to focus on the Raspberry Pi. However, this should allow testing the library's compatibility with other boards with similar architecture. We are excited to hear from the community about possible improvements to this approach.

Thanks to contributions by @​stefanhaustein, @​Haruka0522, @​mpilone, @​dariuszzbyrad, @​taartspi, @​eitch, @​fdelporte.

All changes: Pi4J/pi4j@2.8.0...3.0.1

2.8.0

• Several code and JavaDoc improvements by adding the checkstyle plugin.
• Improvements in loading the Mock providers to build and test Pi4J on a Raspberry Pi.
• Issue #421: Unable to detect board type. Several improvements have been integrated in the board detection to prevent errors when reading the board code.
• Added to BoardModel:
  • Issue #406: Old boards not auto detected. Missing codes have been added for Model 1 boards.
  • The Raspberry Pi Compute 5. Only the board code c04180 for the 4Gb has been confirmed by Jeff Geerling. The other types are not documented yet. We assume they are a04180, b04180, and d04180, similar to the Compute 4, but will adjust whenever more info is available.
  • The Raspberry Pi 500 with the board code d04190, again confirmed by Jeff who received an evaluation device.
  • The Raspberry Pi 5 with 16GB memory with the board code e04171 (thanks again Jeff).
• Added to BoardReading:
  • Pull request #432: Add Support for Throttled State Parsing and Retrieval
• Improvements in the LinuxFS provider (for Raspberry Pi 5):
  • Pull Request #433: Enhance LinuxFsI2CBus validation with detailed exception messages and comprehensive Javadocs.
  • Pull Request #434: Add SPI support in LinuxFS. No sudo is needed to use SPI.

Thanks to contributions by @​mpilone, @​cniesen, @​geerlingguy, @​dariuszzbyrad, @​taartspi, @​eitch, @​fdelporte.

Special thanks to Dariusz Zbyrad for joining the project and improving the Maven builds with a wrapper for more consistency, for example, in the pi4j-example-devices repository, and other contributions. And also special thanks to Mike Pilone for the initial work for LinuxFS SPI.

... (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)

[gdepuille]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[gdepuille]

@dependabot recreate

[gdepuille]

@dependabot rebase

[dependabot]

Superseded by #243.