Plugin is generating Assertions entry point in different package when class is added about assertj-assertions-generator-maven-plugin HOT 7 CLOSED

Assertions is generated in the most basic package, i.e. c.b.a.e package since it contains less package than c.b.a.c.i.

Can you tell me what is broken ?

from assertj-assertions-generator-maven-plugin.

Assertions class is being moved after adding

<class>c.b.a.e.AnotherClass</class>

Existing tests which are using c.b.a.c.i.Assertions are not compiling anymore.

from assertj-assertions-generator-maven-plugin.

The simplest solution is to get rid of c.b.a.c.i.Assertions and use c.b.a.e.Assertions.

We could add a configuration option to set where Assertions class will be generated but if you haven't set this option at your first run your problem will still be there as the plugin will have to to generate Assertions somewhere.

WDYT ?

from assertj-assertions-generator-maven-plugin.

The option is good idea.

Also, I found out, that generator is generating Javadoc comments, that are causing Javadoc generation failure.

Creates a new </code>{@link SomeObjectAssert}</code> to make assertions on actual SomeObject.

As you can see there are two closing tags which are making Javadoc generator unhappy.

Should I post issue about this?

from assertj-assertions-generator-maven-plugin.

No, I'm gonna create the issue and fix it right away, thanks

from assertj-assertions-generator-maven-plugin.

Hi,

I saw too late that you were already going to address this issue. I needed the fix and have just made a modification that adds an optional package name under which the entry point class will be generated. You might want to check out my fork at https://github.com/floppywaste/assertj-assertions-generator-maven-plugin and https://github.com/floppywaste/assertj-assertions-generator

It's tested and works fine for me.

from assertj-assertions-generator-maven-plugin.

I have integrated your solution, thanks.

from assertj-assertions-generator-maven-plugin.