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

Clean project with debezium-quarkus-outbox fails with BuildException #11820

Closed
rsvoboda opened this issue Sep 2, 2020 · 2 comments
Closed

Clean project with debezium-quarkus-outbox fails with BuildException #11820

rsvoboda opened this issue Sep 2, 2020 · 2 comments
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@rsvoboda
Copy link
Member

rsvoboda commented Sep 2, 2020

Clean project with debezium-quarkus-outbox fails with BuildException.
There are no code changes, just generated skeleton application.

java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.arc.deployment.ArcProcessor#validate threw an exception: javax.enterprise.inject.spi.DeploymentException: javax.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type javax.persistence.EntityManager and qualifiers [@Default]
	- java member: io.debezium.outbox.quarkus.internal.EventDispatcher#entityManager
	- declared on CLASS bean [types=[io.debezium.outbox.quarkus.internal.EventDispatcher, java.lang.Object], qualifiers=[@Default, @Any], target=io.debezium.outbox.quarkus.internal.EventDispatcher]
	at io.quarkus.arc.processor.BeanDeployment.processErrors(BeanDeployment.java:990)
	at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:234)
	at io.quarkus.arc.processor.BeanProcessor.initialize(BeanProcessor.java:122)
	at io.quarkus.arc.deployment.ArcProcessor.validate(ArcProcessor.java:391)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at io.quarkus.deployment.ExtensionLoader$2.execute(ExtensionLoader.java:932)
	at io.quarkus.builder.BuildContext.run(BuildContext.java:277)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:2046)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1578)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1452)
	at java.base/java.lang.Thread.run(Thread.java:834)
	at org.jboss.threads.JBossThread.run(JBossThread.java:479)
Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type javax.persistence.EntityManager and qualifiers [@Default]
	- java member: io.debezium.outbox.quarkus.internal.EventDispatcher#entityManager
	- declared on CLASS bean [types=[io.debezium.outbox.quarkus.internal.EventDispatcher, java.lang.Object], qualifiers=[@Default, @Any], target=io.debezium.outbox.quarkus.internal.EventDispatcher]
	at io.quarkus.arc.processor.Beans.resolveInjectionPoint(Beans.java:494)
	at io.quarkus.arc.processor.BeanInfo.init(BeanInfo.java:362)
	at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:226)
	... 14 more

Reproducer:

mvn io.quarkus:quarkus-maven-plugin:1.7.1.Final:create \
    -DprojectGroupId=org.acme \
    -DprojectArtifactId=getting-started \
    -DclassName="org.acme.getting.started.GreetingResource" \
    -Dpath="/hello" \
    -Dextensions="quarkus-outbox"
cd getting-started
mvn package
@rsvoboda rsvoboda added the kind/bug Something isn't working label Sep 2, 2020
@geoand
Copy link
Contributor

geoand commented Sep 3, 2020

I am almost certain this has been fixed in the latest debezium release.

cc @gunnarmorling @gsmet

@gsmet
Copy link
Member

gsmet commented Sep 3, 2020

Yeah this is known, will be fixed with the upgrade to 1.2.3.Final.

@gsmet gsmet added this to the 1.8.0.Final milestone Sep 3, 2020
@gsmet gsmet self-assigned this Sep 3, 2020
@gsmet gsmet closed this as completed Sep 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants