Version control per module

We deferred it for post-Aurora version.

--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Odd Möller" <odd.moller@cypoint.se> wrote in message
news:buqov6$g72$1@is.intellij.net...

Now that we have modules, how about allowing each module to have separate
VCS settings?

>

There exists an old request
(http://www.intellij.net/tracker/idea/viewSCR?publicId=7480) for multiple
VCS, where Valentin Kipiatkov comments that there should be one version
control per module.

>

///Odd

>
>

Hi,

so do you have it for Pallada?

Regards
Udo

Udo Kleinkop wrote:

Hi,

so do you have it for Pallada?

Regards
Udo

I'm affraid this will be implemented in 5.0 version only. But this is for sure this time cause we die hard need this
ourselves :)

--
Maxim Shafirov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

How about handling settings in a more general way altogether, i.e. allowing all (or most) settings to be defined on either module, project, or global level?
E.g. I'd like to have different code styles for different modules.
NetBeans has this concept and in principal I like it a lot (that principle, not NetBeans :)
I'm sure you guys would manage to make a better GUI for that than NetBeans, though.

Stephen Kelvin wrote:

How about handling settings in a more general way altogether,
i.e. allowing all (or most) settings to be defined on either module, project, or global level?

+10
I sick of changing file types 2 a day when i need to fix some issues in
2 different projects

K

Maxim, make sure you do it first this time in the next EAP. We don't want this to turn out to be a 5.5 feature ;)

Jacques