If you are using Gradle instead of Maven as build tool and your tests uses
Arquillian TomEE remote mode, Arquillian tries to download the required
Apache TomEE version to install it locally and run the tests. The problem
is that the TomEE artifact is downloaded in target directory, and this
directory does mean nothing in Gradle. This affects that when you do a
gradlew clean the installation is not removed since the directory that
Gradle uses for building the application is build. So you end up by not
rally cleaning all the things that were used in during build phase.

I think that there are two solutions, the first one is adding a parameter
to configure where TomEE should be downloaded. Or another one a bit more
smart that is detecting if you are using Maven or Gradle (for example
checking for pom.xml), and act accordantly.

WDYT?

Reply via email to