Robert, Glad to see that you're giving Maven a try.
Maven modules always depends on compiled artifacts that are installed in your repository, not directly on the source of other modules. This is good practice because now you are certain that you depend on pre-built, pre-tested artifacts, rather than on possibly buggy source code. If your two projects are modules of a multi-module project, you can just build the entire project from the parent root. Maven is smart enough to detect that project B is part of the same project and that project A depends on it. Maven will arrange the build reactor sequence in such a way that project B is built and installed before project A. This guarantees that project A will have a fresh version of project B as a dependency. I am not an Eclipse user - hail IntelliJ IDEA ;) - but you could possibly create direct source links (module dependencies) for modules of your parent project. This is usually easier if you're working on more than one module, because the source is directly available in your IDE and code changes appear to be available to the other module. But bare in mind that Maven never depends on the sources of other modules, but on the compiled artifacts. Cheers Jo On 5/30/07, Robert Blixt <[EMAIL PROTECTED]> wrote:
Hi, I'm trying to get a handle on Maven2 (Been using Ant for a while, and this seems to be the next logical step). However, I've stumpled upon some problems. I have two projects (Project A and B). Project A is dependent on project B. (I'm using Eclipse IDE with Maven plugin). I know how to create a jar of project B and make a dependency of that in project A. But I would like to make a dependency directly to the Eclipse project. So I do not need to create a jar each time I've updated project B. Is this possible? What is the preferred way to deal with this? Kind Regards, Robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
