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

[BUG] Bad service configuration file, or exception thrown while constructing Processor object: com/karuslabs/utilitary/AnnotationProcessor #366

Closed
soshimee opened this issue Mar 13, 2022 · 2 comments

Comments

@soshimee
Copy link

Describe the bug
When building, it says Bad service configuration file, or exception thrown while constructing Processor object: com/karuslabs/utilitary/AnnotationProcessor

To Reproduce
Steps to reproduce the behavior:

  1. Build with typist
  2. See error

Expected behavior
I expected it to build, since there are no errors on my IDE.

Environment (please complete the following information):

  • Java Version: 17
  • Platform: Paper
  • Platform Version: 1.18.2
  • Chimera Version: 5.2.0
@soshimee soshimee added the bug label Mar 13, 2022
@Pante Pante self-assigned this Mar 13, 2022
@Pante
Copy link
Owner

Pante commented Mar 13, 2022

Interesting, seems like there's a configuration error in Typist 5.2.0. In hindsight, I completely forgot to bump the version when releasing 5.2.0. Reverting typist to 5.1.0 seems to fix it on my side. In the interim, perhaps you can downgrade to 5.1.0 while I work on a fix.

Pante added a commit that referenced this issue Mar 14, 2022
@Pante
Copy link
Owner

Pante commented Mar 14, 2022

Thanks for reporting the issue, @soshimee ! After looking into the issue, it seems to be due to a misconfiguration in maven-shade for typist, specifically, we were accidentally creating separate shaded artifacts. We've seen released a fix that patches 5.2.0. All that needs to be done is clear you local cache and rebuild the project.

Please do let us know if the issue still persists.

@Pante Pante closed this as completed Mar 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants