btw the same project interdependecies resolution is done in mevenide for netbeans (both for m1 and m2) since that one is an IDE plugin, not maven plugin, it allows to dynamically change the jar/project linking on project open/close. for example if I work on mevenide, then maven dependencies are only referenced as jars in the repo, but once I open the maven-artifact, then the dependency in other projects is changed to point to the project rather then the jar. Assuming the versions in dependency and project match.
projects with modules allow to open multiple projects at once, eg opening the whole maven codebase. Milos On 11/14/05, Kaare Nilsen <[EMAIL PROTECTED]> wrote: > > Ok.. after some thought I need to reevaluate my opinion on this. > I have now played a little with the eclipse plugin, and well.. i must > admit that i like the way it behaves. So using project references for > projects in the same reactor build where the version of the project in > the reactor, and the version of the dependency seems like a good > default behaviour to me. > > > > On 14/11/05, Kaare Nilsen <[EMAIL PROTECTED]> wrote: > > My mistake > > You are right Mark. So it seems like the eclipse plugin does it alot > > like what Brett are describing.. But again.. this is to automagically > > for me ;) > > > > > > > > On 14/11/05, Mark Hobson <[EMAIL PROTECTED]> wrote: > > > The eclipse plugin *does* create different project files depending on > > > where it's run. It uses project references if the other projects are > > > within the reactor build. It's also very particular regarding > > > versions, as this thread details: > > > > > > > http://www.nabble.com/eclipse%3Aeclipse-and-direct-project-references-t488871.html#a1329272 > > > > > > I agree we need to be consistent across IDEs and would like things to > > > be simplified and configurable. > > > > > > Cheers, > > > > > > Mark > > > > > > On 14/11/05, Kaare Nilsen <[EMAIL PROTECTED]> wrote: > > > > Well, no.. > > > > I think that what you are describing is somewhat to magical for me > ;) > > > > You say that the idea plugin creates different projects depending on > > > > where you run the command, i personally finds that very confusing. > In > > > > my opinion a plugin after configured in the module pom (or a parent) > > > > should behave consistently, and create equivalent projects on every > > > > run, not depending on where the command is executed. > > > > > > > > The eclipse plugin creates project references if they share the same > > > > parent pom (i have seen there are ppl out there struggeling with > that, > > > > but in my experience it works) no matter if you run the plugin from > > > > the root or in a subdirectory. > > > > Personally i find this to be a more consise solution. > > > > > > > > hehe, i litteraly can se my self trying to explain it to a coworker. > > > > "Oh.. yeah.. by the way. please do remember to check where your run > > > > your project generation. The result may vary", and then i can > imagine > > > > the look of confusion i would get back ;) > > > > > > > > So If an IDE project is generated for a module in a multimodule > > > > project, it should always by default use project references. > > > > > > > > But then again. perhaps the notion of project generation strategy > > > > would be a cool common setting. > > > > like this (using one of the values inside[] ) > > > > ... > > > > <configuration> > > > > <projectReferenceStrategy> > > > > [direct,directIfSameVersion,repsitory,snapshot-repository] > > > > </projectReferenceStrategy> > > > > ... > > > > > > > > > > > > > > > > On 14/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > Yes, I definitely agree with that. This discussion should be about > the > > > > > default, but be configurable. > > > > > > > > > > So, you say the eclipse plugin does well - is it the same or > different > > > > > to the idea plugin as I described it? > > > > > > > > > > - Brett > > > > > > > > > > Kaare Nilsen wrote: > > > > > > Then supply good default behaviour (where i really do think the > > > > > > current eclipseplugin does a good job). And finally let the > users > > > > > > choose how they want to use it. > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
