hehe, thought gradle was smart enough to adapt any situation ;)

We did the smart solution - not for gradle itself btw - in some cases but
using pom.xml is a weak solution cause you can execute tests in other
directories so being smart involed much more than what we want most of the
time (browsing a tree etc).

however we have "dir" directory which is the temp folder for the container
so we can extract it there: https://issues.apache.org/jira/browse/TOMEE-1708


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>

2016-02-10 13:20 GMT+01:00 Alex Soto <[email protected]>:

> Ok but could we do the smart resolution?
> El 10/2/2016 12:48 a. m., "Romain Manni-Bucau" <[email protected]>
> escribió:
>
> > Hi Alex,
> >
> > you can set  openejb.deployer.cache.folder to build or change test
> > execution dir to build as well
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com>
> >
> > 2016-02-10 5:12 GMT+01:00 Alex Soto <[email protected]>:
> >
> > > 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