8425: Problem importing in Eclipse due to missing awatility 3rd party artefact

[skarsaune]

The Jolokia test plugin requires awaitility

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed (1 review required, with at least 1 Committer)

Issue

• JMC-8425: Problem importing in Eclipse due to missing awatility 3rd party artefact (Bug - P4)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jmc.git pull/668/head:pull/668
$ git checkout pull/668

Update a local copy of the PR:
$ git checkout pull/668
$ git pull https://git.openjdk.org/jmc.git pull/668/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 668

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jmc/pull/668.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[mlbridge]

Webrevs

• 00: Full (8e3e4a32)

[viragpurnam]

Hi @skarsaune, this plugin needs to be added to all target platforms as well under local p2 repository.

[bridgekeeper]

@skarsaune This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[skarsaune]

Hi @skarsaune, this plugin needs to be added to all target platforms as well under local p2 repository.

@viragpurnam : Hmm, this is a test requirement, only needed by a test plugin. So it should not be shipped as part of the product. If it works like this it is fine, if not we have to look at some other mechanism.

[thegreystone]

I think Virag just meant the target platform, where all third party dependencies are exported over a p2.

[skarsaune]

I think Virag just meant the target platform, where all third party dependencies are exported over a p2.

Ok, I can try to include it