It's a bad practice to use a file that is stored under an other project. The best practice is to create a module that store shared files then you add it as a dependency of your project.
Emmanuel On Thu, Dec 10, 2009 at 10:52 AM, Engebakken Geir <[email protected]>wrote: > Thats correct, problem solved. Thank you! > > > Geir > > -----Original Message----- > From: Brent Atkinson [mailto:[email protected]] > Sent: 9. desember 2009 18:33 > To: [email protected] > Subject: Re: Problem with multi module maven project > > You could add the project as a recursive build. This should run it like you > would from the command line if I'm not mistaken. > > Brent > > >>> Engebakken Geir 12/09/09 10:43 AM >>> > We have a multi module maven project that we have added to continuum, by > the parent pom. Continuum then put all subprojects into continuum. But the > problem is that all subprojects are placed in the same directory "level", > that is for us this is : > > /usr/local/continuum/data/working-directory > > All projects are placed in a flat structure there with a numeric id as top > level directory. > > This is a problem for the submodules, as they refer to some files in the > parent project like this : > > ${basedir}/../../wsdl/documentws/document/Document.wsdl > > The ../.. notation from ($basedir) then fails. Any idea how we can fix this > ? > > Geir > > > >
