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
With your strategy, I would have to install very often to see how the changes to B effects A. /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]
