[#IDEADEV-11616] Adding a module should add content roots to VCS

IDEA: Development

Adding a module should add content roots to VCS

Created: 28 Mar 05 02:59 Updated: 06 Nov 08 23:28

Component/s:

Version Control Integration

Fix Version/s:

Undefined

Original Estimate:

1 day

Remaining Estimate:

1 day

Time Spent:

Unknown

Issue Links:

Relates

This issue is related to:
	IDEADEV-11974 Intelligent VCS Project Setup

Build:

3,265

Description

« Hide

I've just noticed on two different projects, that when adding a new module to the project, the source trees are not added to the current version control system.

In one project this then let me refactor and move a file into a non version-controlled sandbox. Which is bad (I'll mention this in another issue )

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Maxim Shafirov - 29 Mar 05 00:22

I wonder how IDEA can guess what version control this newly created module should go to? We do support multiple version controls. Then even we have only one version control like say SVN how it should guess the URL module should be exported to?
On other hand if content directories of the newly created module are all under some version control already those should be automatically picked. Doesn't that work?

[ Permlink | « Hide ]

NNTP User - 29 Mar 05 13:00

It didn't work in this instance in any case...

In the SVN project, I had my original/only module at:

/home/mark/code/projects/jirabrowser/trunk/main

the .ipr is at the ./trunk level, and I created the new module at

/home/mark/code/projects/jirabrowser/trunk/libjira

I would have assumed the libjira directory would have been added under
trunk in the SVN repository.

[ Permlink | « Hide ]

NNTP User - 30 Jul 05 08:54

It didn't work in this instance in any case...

In the SVN project, I had my original/only module at:

/home/mark/code/projects/jirabrowser/trunk/main

the .ipr is at the ./trunk level, and I created the new module at

/home/mark/code/projects/jirabrowser/trunk/libjira

I would have assumed the libjira directory would have been added under
trunk in the SVN repository.

[ Permlink | « Hide ]

NNTP User - 31 Jul 05 00:08

It didn't work in this instance in any case...

In the SVN project, I had my original/only module at:

/home/mark/code/projects/jirabrowser/trunk/main

the .ipr is at the ./trunk level, and I created the new module at

/home/mark/code/projects/jirabrowser/trunk/libjira

I would have assumed the libjira directory would have been added under
trunk in the SVN repository.

[ Permlink | « Hide ]

NNTP User - 14 Dec 05 19:43

It didn't work in this instance in any case...

In the SVN project, I had my original/only module at:

/home/mark/code/projects/jirabrowser/trunk/main

the .ipr is at the ./trunk level, and I created the new module at

/home/mark/code/projects/jirabrowser/trunk/libjira

I would have assumed the libjira directory would have been added under
trunk in the SVN repository.

[ Permlink | « Hide ]

Dmitry Jemerov - 03 Oct 07 22:37

Currently content and source roots are created through IO rather than VFS, so VCS integrations do not receive proper notifications about their creation.