module system: Hard coded paths in .iml file

For some time in the eap, the .iml files contain hard coded paths. This
makes storing the project in cvs, and using it for multiple branches
checked out concurrently or for multiple developers checking out the
project in various locations impossible.

We always maintain three branches: production, eap, and trunk. With the
current eap, I either have to maintian all three version of the project
or copy the project around but search/replace the paths.

How are above scenarios intended to be handled with the final module system?


Please sign in to leave a comment.