You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by Daniel Templeton <da...@cloudera.com> on 2016/11/23 19:21:42 UTC
Build Leakage?
I have two completely separate directories that contain distinct clones
of trunk. In one I'm running "mvn test -Dtest=..." in a loop. In the
other I'm running "mvn clean install -DskipTests". When I do the build,
the test running in the other directory fails with NoClassDefFound.
Are we leaking stuff into some common directory that's being shared
across builds? I see stuff showing up in /tmp, but it's very temporary
and doesn't look like anything that should affect a test.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: Build Leakage?
Posted by Daniel Templeton <da...@cloudera.com>.
Good to know! Thanks, Eric.
Daniel
On 11/23/16 11:43 AM, Eric Badger wrote:
> This is an issue with maven. It uses the same .m2 directory across
> both of the builds unless you specify otherwise and they stomp all
> over each other. What I do to get around this issue is to create 2
> separate .m2 directories with their own unique settings.xml file. The
> settings.xml files are identical except for <localRepository>, which I
> set to different directories for each of them. You can specify the
> settings.xml file on the command line using the "--global-settings" flag.
>
> Eric
>
>
> On Wednesday, November 23, 2016 1:21 PM, Daniel Templeton
> <da...@cloudera.com> wrote:
>
>
> I have two completely separate directories that contain distinct clones
> of trunk. In one I'm running "mvn test -Dtest=..." in a loop. In the
> other I'm running "mvn clean install -DskipTests". When I do the build,
> the test running in the other directory fails with NoClassDefFound.
>
> Are we leaking stuff into some common directory that's being shared
> across builds? I see stuff showing up in /tmp, but it's very temporary
> and doesn't look like anything that should affect a test.
>
> Daniel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> <ma...@hadoop.apache.org>
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> <ma...@hadoop.apache.org>
>
>
>
Re: Build Leakage?
Posted by Eric Badger <eb...@yahoo-inc.com.INVALID>.
This is an issue with maven. It uses the same .m2 directory across both of the builds unless you specify otherwise and they stomp all over each other. What I do to get around this issue is to create 2 separate .m2 directories with their own unique settings.xml file. The settings.xml files are identical except for <localRepository>, which I set to different directories for each of them. You can specify the settings.xml file on the command line using the "--global-settings" flag.
Eric
On Wednesday, November 23, 2016 1:21 PM, Daniel Templeton <da...@cloudera.com> wrote:
I have two completely separate directories that contain distinct clones
of trunk. In one I'm running "mvn test -Dtest=..." in a loop. In the
other I'm running "mvn clean install -DskipTests". When I do the build,
the test running in the other directory fails with NoClassDefFound.
Are we leaking stuff into some common directory that's being shared
across builds? I see stuff showing up in /tmp, but it's very temporary
and doesn't look like anything that should affect a test.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org