assertj / assertj/assertj-generator

FQCN of assertion classes are not replaced in assertions entry point classes when using the generateAssertionsInPackage option.

Open
#122 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
72
Forks
47
Avg merge
1d 16h
Merged PRs (30d)
2

Description

I use generateAssertionsInPackage option like following.

**Project structure**

```text
|-src/main/java
| `-sample/
| `-Foo.java
`-pom.xml
```

**pom.xml**

```xml


sample

sample.assertion

```

Assertion class is generated as `sample.assertion.FooAssert`.

**FooAssert.java**

```java
package sample.assertion;

import sample.Foo;

...

public class FooAssert extends AbstractFooAssert {
```

However assertions entry point classes are generated like following.

**Assertions.java**

```java
package sample.assertion;

...
@javax.annotation.Generated(value="assertj-assertions-generator")
public class Assertions {

...
@org.assertj.core.util.CheckReturnValue
public static sample.FooAssert assertThat(sample.Foo actual) {
return new sample.FooAssert(actual);
}
```

`FooAssert` is written as `sample.FooAssert` (not `sample.assertion.FooAssert`).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.