On 1/11/06, Christopher Cobb <[EMAIL PROTECTED]> wrote: > > -----Original Message----- > > From: Edwin Punzalan [mailto:[EMAIL PROTECTED] > > > > Although, I have to say, when you did some changes on P4, you should be > > building it anyway, right? Because you'll need to run the tests, etc. > > and make sure that everything's still fine. > > But my IDE thinks this is all one big project. I may not have realized that > I was making a change to P4. My smart IDE just "took" me to that source and > I just fixed it. And even if I realized that my change was in a sibling > project, well, that's what computers are for! :) The computer should do as > much for me as it can. > > > And when you build P4, you can just type "mvn install" and that would > > update your local repository. So that when you do try to build P1, mvn > > will get the latest jar in your local repo. > > Yes, that's what I do now. It just seems like an extra step that the > computer should be able to do for me. It seems like all of the information > is there to allow this to happen, we just have to make use of it. Well, uh, > I suppose I could write the plugin. Hmmm...
But if your IDE, or whatever working environment you use, you treat each child project as an individual project, not one big project, then when building P1, you only want to build P1. For those that work this way (and it's how the IDE plugins work by default), transitively building would be a waste of time. For my usage, I can't think of a case I'd ever want this behavior. That's not to say that there's not enough people who do want it to justify the option being added... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
