-
Notifications
You must be signed in to change notification settings - Fork 45
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
After upgrading Micronaut Gradle plugin from 3.2.2 to 3.3.0 fat-JAR application launch crashes with No bean of type [io.micronaut.context.event.ApplicationEventPublisher<io.micronaut.context.event.StartupEvent>] exists #406
Labels
type: bug
Something isn't working
Comments
Bug is not specific to Kotlin, also happens with Java. |
Workaround is to add: tasks.withType(ShadowJar.class).configureEach(ShadowJar::mergeServiceFiles) to your build script |
melix
added a commit
that referenced
this issue
Mar 22, 2022
This commit fixes shadow jar building, by making sure that the generated jar merges service files. Fixes #406
melix
added a commit
that referenced
this issue
Mar 22, 2022
* Fix service files not merged with shadow plugin This commit fixes shadow jar building, by making sure that the generated jar merges service files. Fixes #406 * Upgrade shadow plugin
Thanks for immediate reaction, including workaround. |
tobiasschaefer
added a commit
to tobiasschaefer/micronaut-zeebe-client
that referenced
this issue
Mar 23, 2022
tobiasschaefer
added a commit
to tobiasschaefer/micronaut-camunda-external-client
that referenced
this issue
Mar 23, 2022
tobiasschaefer
added a commit
to tobiasschaefer/micronaut-camunda-bpm
that referenced
this issue
Mar 23, 2022
tobiasschaefer
added a commit
to tobiasschaefer/micronaut-zeebe-client
that referenced
this issue
Mar 23, 2022
tobiasschaefer
added a commit
to camunda-community-hub/micronaut-zeebe-client
that referenced
this issue
Mar 23, 2022
tobiasschaefer
added a commit
to tobiasschaefer/micronaut-camunda-external-client
that referenced
this issue
Mar 23, 2022
tobiasschaefer
added a commit
to camunda-community-hub/micronaut-camunda-external-client
that referenced
this issue
Mar 23, 2022
tobiasschaefer
added a commit
to tobiasschaefer/micronaut-camunda-bpm
that referenced
this issue
Mar 23, 2022
tobiasschaefer
added a commit
to camunda-community-hub/micronaut-camunda-platform-7
that referenced
this issue
Mar 23, 2022
It stills fails for Application Type: #407 applies to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Application should launch smoothly like before the upgrade.
Actual Behaviour
Application's Single-JAR is currently built using following plugin:
id('com.github.johnrengelman.shadow') version '7.+'
After upgrading Gradle Micronaut plugin from
id('io.micronaut.application') version '3.2.2'
to
id('io.micronaut.application') version '3.3.0'
launching the Single-JAR application like so
java -jar build/libs/application-0.1-all.jar
breaks with
reproducibly.
With enabled trace logging (as requested) the following message appears just in front of the one cited above:
Also explicit addition of mentioned library with Kotlin APT via
kapt('io.micronaut:micronaut-inject-java')
doesn't help.None of the application's types explicitly implement mentioned interface
io.micronaut.context.event.ApplicationEventPublisher<io.micronaut.context.event.StartupEvent>
.After switching back to
id('io.micronaut.application') version '3.2.2'
app launches smoothly (with lots of messages regarding bean conditionals due to enabled trace logging of this feature).Steps To Reproduce
See above.
Environment Information
Example Application
No response
Version
3.3.4
The text was updated successfully, but these errors were encountered: