Here’s mvn -v: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T09:41:47-07:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec Java version: 1.8.0_102, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.12", arch: "x86_64", family: "mac" On Wed, Sep 28, 2016 at 11:26 PM, Andrus Adamchik <[email protected]> wrote: > You should be able to successfully run "mvn clean install" or "mvn clean > verify" with clean Maven repo without any prerequisites against most the > DBs on OSX and Linux. E.g.: > > https://builds.apache.org/view/All/job/cayenne-master/378/ > > This is why I am confused about your test failures. I checked the output > file you sent previously - the failures *are* real. Just not reproducible > on my end. > > What's the output of "mvn -v" BTW? > > Andrus > > > > > On Sep 28, 2016, at 8:19 PM, Lon Varscsak <[email protected]> > wrote: > > > > This gets failsafe failure too: > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-failsafe-plugin:2.17:verify > > (integration-test) on project cayenne-server: There are test failures. > > > > Am I wrong in assuming it should compile with tests without issue (from > > clean, no .m2 directory)? > > > > -Lon > > > > On Tue, Sep 27, 2016 at 11:37 PM, Andrus Adamchik < > [email protected]> > > wrote: > > > >> Also if the failures are HSQL-specific (I can't reproduce it, so hard to > >> say), perhaps another way to circumvent the failures is to use another > >> in-memory DB for testing. E.g: > >> > >> mvn clean install -DcayenneTestConnection=derby > >> > >> Not ideal, but who knows, maybe this will also get it unstuck. > >> > >> Andrus > >> > >> > >>> On Sep 28, 2016, at 9:30 AM, Andrus Adamchik <[email protected]> > >> wrote: > >>> > >>> Interesting. Didn't know about -skipTests. > >>> > >>> And another mystery - why do those tests fail in the first place. > >>> > >>> Andrus > >>> > >>> > >>> > >>>> On Sep 28, 2016, at 9:28 AM, Savva Kolbachev <[email protected]> > >> wrote: > >>>> > >>>>> We are reusing test classes from cayenne-server in testing the > client. > >> No > >>>> easy way around that. > >>>> > >>>> Sorry for misunderstanding. I meant that Cayenne should not require > test > >>>> classes from cayenne-server for building cayenne-client without > testing. > >>>> > >>>> It happens when you build with -Dmaven.test.skip=true. On the other > >> hand, > >>>> if you build with -DskipTests, it will not require test classes from > >>>> cayenne-server for building cayenne-client and will work great. > >>>> > >>>> It is important for those, who just takes the latest version from > trunk > >> and > >>>> wants to build sources without testing. So, if they build > >> 4.0.M4-SNAPSHOT > >>>> for the first time and without testing, they might not have > >>>> cayenne-server:jar:tests:4.0.M4-SNAPSHOT > >>>> in the local .m2 repo. > >>>> > >>>> On Wed, Sep 28, 2016 at 8:25 AM, Andrus Adamchik < > >> [email protected]> > >>>> wrote: > >>>> > >>>>> > >>>>>> On Sep 27, 2016, at 11:34 PM, Savva Kolbachev < > [email protected]> > >>>>> wrote: > >>>>>> > >>>>>> So, your .m2 repository doesn't contain > >>>>>> org.apache.cayenne:cayenne-server:jar:tests:4.0.M4-SNAPSHOT, which > is > >>>>>> necessary for the cayenne-client. Not sure that it is a correct > >> behaviour > >>>>> > >>>>> We are reusing test classes from cayenne-server in testing the > client. > >> No > >>>>> easy way around that. > >>>>> > >>>>> Andrus > >>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Best Regards, > >>>> Savva Kolbachev > >>> > >> > >> > >
