In your case, you will need to add shindig-common dependency with test classifier just for test scope.
But, like Henning said, it is a good practice in java world to have a standalone test harness project. I am in favour of this solution. Cheers, Vincent 2008/7/3, Henning P. Schmiedehausen <[EMAIL PROTECTED]>: > Evan Gilbert <[EMAIL PROTECTED]> writes: > > >--000e0cd25cf4c5133d045114bff7 > >Content-Type: text/plain; charset=ISO-8859-1 > >Content-Transfer-Encoding: 7bit > > >Anyone else with an opinion on the location of test code? > > >Also, if we move the code, is it OK for the java/social-api/src/test project > >to depend on the java/common/src/test/project, or is there a better way to > >structure this? > > I don't think you can do that with maven. The test code is not > packaged up in the jar (that is the whole point of it being test > code). What you want is probably a "test-harness" project as proposed, > which contains all the common code as src/java, which is turned into a > shindig-test-harness jar. This jar is then rerferenced by all other > projects in test scope. > > Ciao > Henning > > -- > Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, > 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person > Open Source Consulting, Development, Design | Velocity - Turbine guy > > INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 > Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen > > "Professor Peach in the library with the lead piping!" -- Donna >
