7348: JMC preference options are duplicated

[guruhb]

"General" , "Appearance" and "Keys" had duplicate entry . This was due to some in consistence "org.eclipse.ui.*" Components were used (one with older + latest version which is causing duplicate entry).

Solution : adding "resolution:=optional" resolves the duplicate entry. Restricted the Eclipse UI components to v3.2.0 and less than equal to 4.0.0.

---

Progress

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

Issue

• JMC-7348: JMC preference options are duplicated

Reviewers

• Marcus Hirt (@thegreystone - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 289

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

Using diff file

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

[bridgekeeper]

👋 Welcome back ghb! 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.

[mlbridge]

Webrevs

• 02: Full - Incremental (6db4e6c7)
• 01: Full - Incremental (ffb3ebc1)
• 00: Full (44bfb25e)

[thegreystone]

Comma after year.

[guruhb]

Fixed now.. Please re-check with latest commit

[guruhb]

/integrate

[openjdk]

@guruhb 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:

7348: JMC preference options are duplicated

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 1 new commit pushed to the master branch:

• bba7e41: 7349: JFR Parser struct types hashcode is not stable

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

Going to push as commit 76f5a56.
Since your change was applied there has been 1 commit pushed to the master branch:

• bba7e41: 7349: JFR Parser struct types hashcode is not stable

Your commit was automatically rebased without conflicts.

[openjdk]

@guruhb Pushed as commit 76f5a56.

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