Hi Referencing a files in another module using relative paths is an anti-pattern. One reason for this is that it will break your build if you are using a build server, like Jenkins. The build server will check out each module into a separate folder, which is not in the same folder structure that your project is using.
The best practice way of sharing resources like configuration files is storing them in an archive that is deployed to your repository. When that is done you can either use it as a dependency, making the resources available on the class path, or use the dependency:unpack goal to extract the files to wherever you want them. On 2011-07-20 13:10, Cem Koc wrote: > @stephenconnolly > > Sorry but I could not understand your point exactly. Could you explain a > little bid more? You mean because of being at another folder such as my > repository it will point somewhere else? > > Thanks > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Relative-path-to-parent-directory-at-multi-module-maven-project-tp4611798p4615533.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
