7512: Update lz4-java and remove the osgi bundle name override

[bric3]

The core library dependency decalred in maven is aligned with the one in the .target files, 1.8.0.

Also I noticed the lz4-java library has an OSGI bundle symbolic name: lz4-java, introduced in 1.3.0 : https://github.com/lz4/lz4-java/pull/39/files#diff-e3399fe1dc27b086e517883c6cab943edbfab64139839c965b14db8d11c8a99aR1-R4
However probably due to some previous bugs this required an override, done here, but this may not be necessary anymore. Hence this PR tries to use the actual osgi name.

The change is little, and hopefully won't ripple beyond.

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-7512: Update lz4-java and remove the osgi bundle name override

Reviewers

• Marcus Hirt (@thegreystone - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/356/head:pull/356
$ git checkout pull/356

Update a local copy of the PR:
$ git checkout pull/356
$ git pull https://git.openjdk.java.net/jmc pull/356/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 356

View PR using the GUI difftool:
$ git pr show -t 356

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/356.diff

[bridgekeeper]

👋 Welcome back bric3! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[thegreystone]

Will need to also update the new targets. Let's take this one after #360 and #361.

[mlbridge]

Webrevs

• 03: Full - Incremental (e72ce0a9)
• 02: Full - Incremental (661c8750)
• 01: Full (f813fefe)
• 00: Full (56bb8157)

[thegreystone]

Hi @bric3 - got to resolve the conflicts (just accepting that the files have been deleted).

[bric3]

@thegreystone Done

[thegreystone]

There is no need to force push changes. The tooling will take care of the squashing and merging automatically. It's actually easier to do the review if changes aren't force pushed.

[bric3]

Noted

[openjdk]

@bric3 This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

7512: Update lz4-java and remove the osgi bundle name override

Reviewed-by: hirt

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@thegreystone) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[thegreystone]

Hi @bric3! Please type /integrate in a comment to integrate this PR.

[bric3]

/integrate

[openjdk]

@bric3
Your change (at version e72ce0a) is now ready to be sponsored by a Committer.

[thegreystone]

/sponsor

[openjdk]

Going to push as commit 9ec05b3.

[openjdk]

@thegreystone @bric3 Pushed as commit 9ec05b3.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.