Feature Proposal: Configuration file rollback

I am curious what others think about this feature ?
It would be nice if IJ could roll back --all-- of its configuration settings to a prior point.
Those files are already kept in the Local VCS so the information is there.
My main use case is when I imported a Maven module/project:
     1) Either IJ wipes out or corrupts my other modules especially the Maven paths.
     2) The Maven import takes hours either trying to resolve dependencies (Even with the latest EAP)
     3) Name your own reason.

I realize IJ would probably have to restart, but that would still save so much time and frustration.

10 comments
Comment actions Permalink

Hello Rob,

So how exactly is this feature different from simply rolling back the .ipr/.iml
files via Local History manually?

I am curious what others think about this feature ?
It would be nice if IJ could roll back all of its configuration
settings to a prior point.
Those files are already kept in the Local VCS so the information is
there.
My main use case is when I imported a Maven module/project:
1) Either IJ wipes out or corrupts my other modules especially
the Maven paths.
2) The Maven import takes hours either trying to resolve
dependencies (Even with the latest EAP)
3) Name your own reason.
I realize IJ would probably have to restart, but that would still save
so much time and frustration.

---
Original message URL:
http://www.jetbrains.net/devnet/message/5250885#5250885

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

If IntelliJ performed the rollback then there is less chance of errors or mismatches between projects file .ipr and module files .iml.
Even though the .iml and .ipr are in the local history I doubt rolling back these files would cause IntelliJ to reload the configurations while it was running.
It's also my conjecture that when IJ exits it would overwrite the one or more of the rolled back files with whatever was in memory, hence creating a mismatch.
Simply put I don't think its possible to do it manually reliably.

1) All modules and project files would be rolled back to the same state/date no exceptions. Users wouldn't/couldn't rollback file by file. This means fewer message on the list and fewer Tracker bug reports related to mismatches in rolled back configurations files.
    If other users are like me I probably average 3 (.iml) files per module because I have 3 or 4 versions of the project with different mixes of modules. I wouldn't have to remember which .iml belong to which .ipr.
2) Once rolled back IJ would NOT write pending configuration thats in memory to the configuration files.
3) IJ would immediately shutdown then restart to reload the configuration files. If IJ can detects changes in the .iml & ,ipr files then reloads w/o restarting thats all the better, but I doubt it can do so w/o changing --alot-- of code.

0
Comment actions Permalink

I am assuming since no others replied that there isn't a general demand/need to rollback the IntelliJ configuration?

0
Comment actions Permalink

Actually, I do like the the configuration file rollback idea.  Don't know what my vote's worth, but count me in!

0
Comment actions Permalink

In all fairness I should also say that its not only IJ I wish had this feature. I dread fixing eclipse configuration files because I have broken them by reimporting a maven project into an existing eclipse project. Luckly, I only use eclipse every 6 months to do what IJ can't for unit testing and a very few other things.

-Rob

0
Comment actions Permalink

Just to see how many votes this gets I filed:

http://youtrack.jetbrains.net/issue/IDEA-53698

The reasons sound compelling to me, :), and I hope most EAP users agree.and vote.

0
Comment actions Permalink

Rob, you mentioned that Maven import takes hours.
Was it a turn of speech or it is really so? 8)
How bit is the project, do you use internal repository mirrors?

0
Comment actions Permalink

My setup is complicated by the fact that Maven and IntelliJ cannot access the Internet.
Our maven repository is kept locally on our machine and has all the jars needed to compile, test and deploy.

Maven imports for version of IJ before 9.0.1 did take hours, and in many cases locked up.
This was also true of the 8.0, 8.1 to 8.1.2 version of IJ. I believe 8.1.4 was improved
I reimported with the 94.X builds and the process takes about 30 minutes for my setup,
and went smoothly except for one bug that I reported.

My experience/history with maven importing is that it works for one or two point releases or EAP builds then is broken for for one or two point releases.
I expect this trend to continue into the future. My assumption is that testing all possible import options is complex, and maven users are creative in how they write their pom's!


-Rob

0
Comment actions Permalink

Is it possible to you to make a stripped project (pom files only preserving the directory structure)?
I would like to profile long importing.

0

Please sign in to leave a comment.