-
Notifications
You must be signed in to change notification settings - Fork 42
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
FQCN of assertion classes are not replaced in assertions entry point classes when using the generateAssertionsInPackage option. #122
Comments
Its a bug then, thanks for reporting this ! |
Is there any updates for it? |
Nope, I unfortunately don't have the time to work on the generator project these days :( |
tbarabanov
pushed a commit
to tbarabanov/assertj-assertions-generator
that referenced
this issue
Aug 28, 2023
Open
tbarabanov
pushed a commit
to tbarabanov/assertj-assertions-generator
that referenced
this issue
Aug 28, 2023
tbarabanov
pushed a commit
to tbarabanov/assertj-assertions-generator
that referenced
this issue
Aug 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use generateAssertionsInPackage option like following.
Project structure
pom.xml
Assertion class is generated as
sample.assertion.FooAssert
.FooAssert.java
However assertions entry point classes are generated like following.
Assertions.java
FooAssert
is written assample.FooAssert
(notsample.assertion.FooAssert
).The text was updated successfully, but these errors were encountered: