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
{{ message }}
This repository was archived by the owner on Dec 3, 2018. It is now read-only.
While integrating MapStruct for #127, it became necessary to customize the JUnit run configuration within IntelliJ in order for it to compile the ExploratoryMapper in the test sources (it had struggled with it in main sources too, but I think it ought to be able to work with either).
The current workaround is: Run > Edit Configurations > Defaults > JUnit > Before launch > Add Maven Goal > compiler:testCompile, then delete or amend any existing JUnit run configurations.
No workaround is needed to run mvn clean test in the terminal. I suspect there're a better way for maven to signal the additional step to IntelliJ, or a cleaner way to detect it. Suggestions welcome.
While integrating MapStruct for #127, it became necessary to customize the JUnit run configuration within IntelliJ in order for it to compile the
ExploratoryMapperin the test sources (it had struggled with it in main sources too, but I think it ought to be able to work with either).The current workaround is: Run > Edit Configurations > Defaults > JUnit > Before launch > Add Maven Goal > compiler:testCompile, then delete or amend any existing JUnit run configurations.
No workaround is needed to run
mvn clean testin the terminal. I suspect there're a better way for maven to signal the additional step to IntelliJ, or a cleaner way to detect it. Suggestions welcome.