5 comments
Comment actions Permalink

Hi Andrew,

Do you mean simultaneously? What do you mean by 'safe'?

0
Comment actions Permalink

Arina,

 

I mean a single IDEA instance switching between projects containing - among others - the same module.

By 'safe' I mean an absence of unexpected side effects (any kind of project inconsistency) during normal IDE using.

0
Comment actions Permalink

Thank you Andrew.

An iml file contains settings for content roots, dependencies and facets for a module. If you add a new module to your project using the existing iml, you get a snapshot of that iml's module with the same settings, and the module is also added to the .idea/modules.xml project configuration file. Changing the module's settings then may lead to changes in the iml file. Yet the iml itself does not depend on .idea directly and can be reused in different projects.

If you use Maven or Gradle, iml files can be disregarded.

0
Comment actions Permalink

Arina, Ok, thanks, so in general case it would be better to deal with different iml files referencing the same module root. Then the question is: what is that handy way to separate iml file with module root dir?

0
Comment actions Permalink

If you just want to edit the source code of a certain module located in ProjectA from within ProjectB, you can create a new module in ProjectB and point it to the folder with the sources that you want to edit.

0

Please sign in to leave a comment.