It goes back to before the shade changes. If you have a multi module maven project, you need to run install before running compile or test because the reactor doesn't automatically include all siblings. It's a pain in ass, but never so much that I would go looking at maven internals.
-Ivan On Thu, Jun 05, 2014 at 09:38:08PM -0700, Sijie Guo wrote: > We should document the step on how to run test somewhere. Due to the usage > of maven-shade-plugin for backward compatibility testing, ways like 'mvn > test -pl :bookkeeper-server -am' would fail on a fresh checkout. since the > shade plugin is only able to run at 'package' phase. if we don't run 'mvn > install' before, running tests would fail due to missing compat-deps > dependencies. > > On Wed, Jun 4, 2014 at 1:59 AM, Ivan Kelly <iv...@apache.org> wrote: > > > On Tue, Jun 03, 2014 at 10:18:03PM -0700, Jaln wrote: > > > I met another issue when compiling the bookkeeper, > > > > > /bookkeeper-4.2.2/bookkeeper-server/src/test/java/org/apache/bookkeeper/test/TestBackwardCompat.java:[70,44] > > > error: package org.apache.bk_v4_0_0.bookkeeper.conf does not exist > > > > > > Do I need to install previous version first? Thanks for your help. > > just doing a mvn install from the top level of the bookkeeper project > > should fix it. > > > > -Ivan > >
