Ok it wasn't apparent to me how that would be useful and I definitely appreciate your explanation. I can definitely see the benefits now.
The only reason I would say to make it optional is to simply make it act more like the previous release. When we first downloaded the 0.0.10 update our projects failed all over. At first I thought it was because of this new feature but now I'm seeing that it has more to do with the 0.0.10 plugin not using the settings.xml file which points us to our internal repositories. I'm definitely anxiously awaiting the fix for that. Again...thanks for clarifying all this! --Rudy -----Original Message----- From: Eugene Kuleshov [mailto:[EMAIL PROTECTED] Sent: Friday, March 23, 2007 3:40 PM To: [email protected] Subject: Re: [m2eclipse-user] Matching dependencies references as projectsautomatically? [EMAIL PROTECTED] wrote: > I'm not saying it doesn't work. It does exactly what it says the > feature is suppose to do. I just don't understand why that is a > "feature" to begin with and why it wouldn't be optional to work that > way? > The main reason is to streamline development. I.e. you don't have to deploy jars to the repository when you need to run or debug something in Eclipse. It also makes much easier to navigate trough the code because you always have source (as long as it is in the Workspace). We had 38 votes for this feature, so it is actually quite popular functionality. See MNGECLIPSE-59. So, said that, can you please reply to my question, what exactly you will gain by disabling this feature? As for making it optional, we have request for this in JIRA. If one want to contribute a patch I don't see why we can't take it. regards, Eugene --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
