You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
io.quarkus.qute.deployment.MessageBundleException: Message bundle method turnEmailWillBeSent() not found on: com.iarchiva.EmailBundles$started
If I rename "interface started {" to "interface rstarted {" the initial part of the name does not match and there is no issue.
Expected behavior
I expect no name collision between "started" and "startedValidator".
Actual behavior
Names collide being different.
How to Reproduce?
Having two interfaces that start with the same string.
Output of uname -a or ver
Microsoft Windows [Versión 10.0.22631.3296]
Output of java -version
openjdk version "21" 2023-09-19 OpenJDK Runtime Environment GraalVM CE 21+35.1 (build 21+35-jvmci-23.1-b15) OpenJDK 64-Bit Server VM GraalVM CE 21+35.1 (build 21+35-jvmci-23.1-b15, mixed mode, sharing)
Quarkus version or git rev
3.9.2
Build tool (ie. output of mvnw --version or gradlew --version)
Gradle 8.6
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
In this kind of situation:
The following error appears:
If I rename "interface started {" to "interface rstarted {" the initial part of the name does not match and there is no issue.
Expected behavior
I expect no name collision between "started" and "startedValidator".
Actual behavior
Names collide being different.
How to Reproduce?
Having two interfaces that start with the same string.
Output of
uname -a
orver
Microsoft Windows [Versión 10.0.22631.3296]
Output of
java -version
openjdk version "21" 2023-09-19 OpenJDK Runtime Environment GraalVM CE 21+35.1 (build 21+35-jvmci-23.1-b15) OpenJDK 64-Bit Server VM GraalVM CE 21+35.1 (build 21+35-jvmci-23.1-b15, mixed mode, sharing)
Quarkus version or git rev
3.9.2
Build tool (ie. output of
mvnw --version
orgradlew --version
)Gradle 8.6
Additional information
No response
The text was updated successfully, but these errors were encountered: