In my opinion, giving the choise to the individual developer would be the best solution. When plugins tries to get "too smart" they often fail, and a lot of discussions appear. It should not be the responsibility of the plugin writer to tell people how they must manage their IDE's projects. Rather the plugin writers should provide good default behaviour and then allow the users of the plugin to change that behaviour if it does not suit their needs. Lets take a project i am in as an example: We have currently 22 modules/projects in our reactor, and our developers works on one or possible 2 or 3 concurrently. Due to how the eclipse plugin currently works each developer needs to have their workspace cluttered with 20 projects they are not working on, and really don't care about. As the one respopnsible of introducing maven to the team, I do come short of explaining to them why they have to have all the projects open. And if some of you out there could come up with the answer here, then honestly you are not really listening to what they are saying. And as i am sayning in the issue http://jira.codehaus.org/browse/MNG-955 Why do we really need to make this so difficult.
So to make a long story short. My opinion is: Yes it would be a good idea to have the plugins behave consistenly, they perhaps could share a configuration object that holds the common settings. 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. On 14/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > Can we discuss how to make the ide plugins behave consistently? It > appears that, in particular, there are a lot of discussions about > Eclipse and direct project references, and as I'm not a user I don't > really follow them - but I'm concerned that they might be arriving at a > different solution to what is already in place for the idea plugin. > > So, could folks provide feedback on this strategy, and if there are any > other places that might differ (eg source/javadoc binding), please > comment on that. > > For project references: the idea plugin uses a reference if and only if > the project exists in the reactor - ie, you run it from the root and it > creates all the files and the single project file. If run from a > subdirectory later, it will not create a link, but use the JAR from the > repository. > > I think I'd want to enhance that to use a reference if it is found in > the USD/workspace - but that's not there just yet as there isn't an API > for the USD, it's only used in finding parent POMs. > > Thoughts? > > - Brett > > --------------------------------------------------------------------- > 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]
