> Which pom.xml? From the module modules/spark? Yes.
> As I understand maven, test will be executed using dependencies from the reactor, not from local repository. I don't get what is the point. Did you try to reproduce issue? Or should I provide full traces to you? > What am I missing? I see that whole build process is done in a very strange way. Because of flatten plugin. I described and able reproduce(both locally and on TC) specific issues that turns whole pom.xml into the mess. I'm pretty sure that source of issue is flatten plugin. I'm not the first person who got this errors. My propositions are: 1. Let's discuss how we should fix it. 2. Let's fix it! 2018-03-01 15:35 GMT+03:00 Petr Ivanov <mr.wei...@gmail.com>: > > > 2. run: > > > > `~/src/ignite/modules/spark> mvn install -U > > -Plgpl,examples,scala,-clean-libs,-release,ml > > -Dtest=org.apache.ignite.testsuites.IgniteRDDTestSuite > > -Dmaven.javadoc.skip=true -DfailIfNoTests=false` > > > > It will execute OK, because maven uses pom.xml from source. > > Which pom.xml? From the module modules/spark? > Also there is no profiles lgpl,examples,scala,-clean-libs,-release,ml in > that module. > > > > > 3. run(only root dir is changed) > > > > `~/src/ignite/> mvn install -U > > -Plgpl,examples,scala,-clean-libs,-release,ml > > -Dtest=org.apache.ignite.testsuites.IgniteRDDTestSuite > > -Dmaven.javadoc.skip=true -DfailIfNoTests=false` > > As I understand maven, test will be executed using dependencies from the > reactor, not from local repository. > > > What am I missing?
