Until now, BWMaven had a call to FCUnit test goal in the test phases of bw-ear and projilb packagings. The execution was triggered only when the FCUnit Projlib was declared as a dependency.
The goal is to avoid this mechanism and to have _two independent plugins_ and use the standard Maven way of declaring plugins.
Until now, BWMaven had a call to FCUnit test goal in the test phases of bw-ear and projilb packagings. The execution was triggered only when the FCUnit Projlib was declared as a dependency.
The goal is to avoid this mechanism and to have _two independent plugins_ and use the standard Maven way of declaring plugins.