Sharing project settings via Subversion, TMate, and/or Team Server

Up until now, I have been the sole IntelliJ IDEA user in an Eclipse shop. I am finally on a project where I specified the IDE for the team. We will all be using Intellij IDEA.

My question is this: What is the best way for all members of the team to share common project and development environment configurations?

I assume that the *.ipr and *.iml files should be checked into source control (svn in our case).
Are there any other files that should be under source control?
Can we share inspection settings?
Can we share code style settings?
Can we share custom file/live templates?
etc.

Is this easy to do?
Is there any support or plan to support this under the TMate?
Is there any support or plan to support this under the Team Server?

Thanks,

Tim

4 comments
Comment actions Permalink

Hello Tim,

TH> Up until now, I have been the sole IntelliJ IDEA user in an Eclipse
TH> shop. I am finally on a project where I specified the IDE for the
TH> team. We will all be using Intellij IDEA.
TH>
TH> My question is this: What is the best way for all members of the
TH> team to share common project and development environment
TH> configurations?
TH>
TH> I assume that the *.ipr and *.iml files should be checked into
TH> source control (svn in our case).

Right.

TH> Are there any other files that should be under source control?

No.

TH> Can we share inspection settings?

In Demetra, you can.

TH> Can we share code style settings?

You can.

TH> Can we share custom file/live templates?

Not right now, as far as I know.

TH> Is this easy to do?

The things which are possible, are easy. :)

TH> Is there any support or plan to support this under the TMate?
TH> Is there any support or plan to support this under the Team Server?

No, this is all core IDEA functionality with no additional support in other
products.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Right now inspection/format/code-coloring and such can be imported and exported, and they can be bound to an individual project, but can't really be shared. True sharing would involve (at minimum) some central repository, and automatic update. I had thought this was in scope for TeamServer (maybe 1.1 or 2.0)?

--Dave Griffith

0
Comment actions Permalink

Whoops, just saw that the roadmap had been updated, and these descoped. Hope they show up in 1.1 or 2.0.

--Dave Griffith

0
Comment actions Permalink

Here is another voice hoping this stuff makes it into 1.1 or 2.0. I know all companies have to make a feature call for each release, but true sharing of configurations will finally solidify the product across large dev teams. We already have a solid automated build process with unit test execution code coverage, static analysis etc.. so more team enablement/standardization is what I am looking for.

0

Please sign in to leave a comment.