good call ron specifically http://stackoverflow.com/questions/2334640/maven-how-to-test-two-modules-with-the-same-tests-in-a-third-module
so you'll wqant to create a base test-suite of abstract classes in the parent then each of the child modules will extend the base test-suite (already defined in the parent) hth, Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Sat, 9 Apr 2011 17:07:12 -0400 > From: [email protected] > To: [email protected] > Subject: Re: SV: [eclipse-plugin] Dependency to workspace projects > > On 09/04/2011 1:19 PM, Ludwig Magnusson wrote: > > The situation is this: > > A depends on B > > ... and I am working on B. > > I want to be able to see how changes in B affects projects like A that will > > be using B > It is called testing. > You want to write B to a spec and test the API that A will use, in a > test suite that is part of B. > > > > With your strategy, I would have to install very often to see how the > > changes to B effects A. > > > Only after B passes its tests. > > Ron > > > /Ludwig > > > > -----Ursprungligt meddelande----- > > Från: [email protected] [mailto:[email protected]] > > Skickat: den 9 april 2011 16:05 > > Till: Maven Users List > > Ämne: Re: [eclipse-plugin] Dependency to workspace projects > > > > I always thing 'resolve workspace dependencies' is a bad idea. Better > > install in local repo. But surely should work for single project. Then you > > would pick everything up from project/lib. Can see why may want to do this > > > > ------Original Message------ > > From: Ludwig Magnusson > > To: [email protected] > > ReplyTo: Maven Users List > > Subject: [eclipse-plugin] Dependency to workspace projects > > Sent: 9 Apr 2011 10:40 > > > > Hello! > > > > I know that the maven-eclipse-plugin somehow can figure out that a > > dependency actually exists as a project in workspace and therefore add that > > project to the build path instead of trying to download a jar-file from a > > remote repository. > > > > My question is: > > > > Is this possible for any dependency or just multi-module-projects? > > > > > > > > In my case, the project is NOT multi-module. > > > > > > > > /Ludwig > > > > > > > > > > Sent using BlackBerry® from Orange > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
