Greetings, On Tue, Jun 5, 2012 at 8:01 AM, Simon Haegler <[email protected]> wrote: > i am planning to write or extend a scm plugin with support for eclipse > project set files. psf's are an easy way to populate an eclipse workspace if > the source code repository has a different directory layout than the eclipse > workspace.
It's generally considered to be a (very) bad practice to include these types of per-user configuration files inside the SCM. Check out most svn:ignore and .gitignore in the root directory of any project for further reference; you'll almost certainly see .classpath, .project, .settings for eclipse, *.iml, *.ipr, *.iwl, *.swp for intellij, and nbproject for netbeans. > the question is: how to start? should i look at a kind of meta-scm plugin or > rather directly enhance the existing scm plugins? > any input is welcome! I've read your message twice and it still isn't clear to me what you're trying to accomplish. Can you provide a use case for how this enhancement would be exploited? Would it echo m-eclipse-p functionality? http://maven.apache.org/plugins/maven-eclipse-plugin/ -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
