Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix jetcd-all which was broken under OSGi (#382) #385

Merged
merged 1 commit into from
Sep 7, 2018

Conversation

vorburger
Copy link
Member

@vorburger vorburger commented Sep 6, 2018

This fixes #382. It builds on top of and uses #386.

Read commit message and JavaDoc in PaxExamWrapperTest for further details.

@lburgazzoli
Copy link
Collaborator

it's failing :)

and ensure future non-regression by making the
ClientServiceTest actually "do something" now (before
it dit not really).  This can only work if we have an etcd locally running
("sudo systemctl start etcd") ... so we need to actually start a server,
like the tests in jetcd-core do, for this test to pass on CI, and really
prove that jetcd-all could be loaded and used (!) under OSGi.

For this, we use the new launcher artifact introduced in previous commits.

It's a bit of a PITA to use launcher (based on testcontainers) with Pax Exam.
We solve this by introducing the PaxExamWrapperTest which uses JUnitCore to
programmatically launch ClientServiceChecks (formerly ClientServiceTest).
To make it clear that jetcd-launcher does not work under OSGi, we do not
package it as a bundle anymore, so rm maven-bundle-plugin / MANIFEST.
@vorburger vorburger changed the title Issue383 fix broken osgi fix jetcd-all which was broken under OSGi (#382) Sep 6, 2018
@vorburger
Copy link
Member Author

it's failing :)

No - not anymore! 😄

@lburgazzoli lburgazzoli merged commit 203e17f into etcd-io:master Sep 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants