I presume you have this use-case in your IDE, since Maven will NEVER use the source-code of another project and always refers to the packaged version in your repository.
What you need is a 'build-project', which contains both projects as modules. Then Maven will recognize they need eachother and build them in the correct order. If you use the eclipse-plugin (not sure about other IDEs, I've only used eclipse so far), the projects will get source-code references to eachother in eclipse. Look at this thread, were I already discussed this: http://www.nabble.com/Dependency-on-another-project-tf4771718s177.html#a13649552 On Friday 09 November 2007 12:34, Hugo Palma wrote: > I have a use case where i am developing two projects, and project A > depends on project B. > > What i want to do is a mvn clean compile under project A directory and > it will also compile project B and use it's classes as a dependency. > Sounds simple enough but i can't seem to be able to get this use case > working. > > The problem is that if i declare the dependency to project B in the > project A pom maven will always look for the installed artifact of B, > which isn't what i want because i don't want to have to install B every > time i try to compile A. > > So i guess what i'm looking for is a way to declare that project A > depends on project B current source code and not it's installed artifact. > > Am i making any sense ? > > Thanks in advance. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
