I must say.. I think it's rather arrogant to assume to know what my prerequisites and goals are when all I've done is to ask how to set up my eclipse environment. I wanted to do it to get an initial idea of how much work different strategies would force upon the end users, and the project itself. I have not written any specs, or tests at this moment because they would be a waste of time. Planning on that level is not what I need. I have not even made the entire project compile, and still I have found what I was looking for.
I asked a question, got an answer and that answer made my day efficient and well spent. And Jörg Schaible is the hero of the day for supplying the answer. I am very thankful for the opportunities given to me by the software and community created by ASF. Please trust me to use it in a good way. When I contribute to an ASF-project. The code will be tested to the best of my ability, I promise. /Ludwig -----Ursprungligt meddelande----- Från: Ron Wheeler [mailto:[email protected]] Skickat: den 9 april 2011 23:07 Till: [email protected] Ämne: Re: SV: [eclipse-plugin] Dependency to workspace projects On 09/04/2011 1:19 PM, Ludwig Magnusson wrote: > 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 It is called testing. You want to write B to a spec and test the API that A will use, in a test suite that is part of B. > With your strategy, I would have to install very often to see how the > changes to B effects A. > Only after B passes its tests. Ron > /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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
