+1 And have all paths be relative to ease sharing across multiple platforms.
Jonas Envall wrote: > I couldn't agree more and I have proposed this to this list before. It > would be > really nice to divide the configuration in two. > > /Jonas > > Gu�laugur S. Egilsson wrote: > >>> I think what he is saying is that if the file read in is bogus (that >>> is from >>> an older, unsupported version for which there is no migration path, >>> then the user should be >>> prompted before IDEA overwrites the project file (destroying it). >>> >> >> To say the least. But the real root of the problem is the mixing of >> two concepts in the project file, the project configuration and >> the user session configuration. Those two should really be separated >> into two files. I consider the project configuration to be a source file >> you need to store in version control, while I don't care a bit about >> whether the user session information is lost or not. It follows that >> the IDEA should ask when saving the project configuration, while >> the session settings can be saved automatically... >> >> >> _______________________________________________ >> Eap-list mailing list >> [EMAIL PROTECTED] >> http://www.intellij.com/mailman/listinfo/eap-list >> > > > > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list > > . > _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
