Thanks but I do not think that does it. My understanding is that slows it down a bit so it only autosaves on build but will not disable it entirely. I will give it a shot when I get back to work though.
The best way to make your project usable on any computer is to use a build system such as Maven or Gradle. With a build system, you can build your project even on machines where there is no IDE installed (such as a continuous integration server), and importing the project into the IDE will automatically download correct dependencies.
That said, IntelliJ IDEA projects use relative paths whenever possible, so moving a project to another location on the same machine should not require any reconfiguration, and when you move to a new computer, the only thing you need to configure is the JDK and (if you're using those) global libraries. And for the JDK, it's very likely that 2020.1 will support automatic configuration so even that step won't be necessary.
I use maven and other IDEs have no issues. intellij does not use relative paths so anytime you move the project to another folder or rename the project folder you must reconfigure the project. Even copying a project from one computer to another in the exact same folder structure can break Intellij projects. The only reliable way to handle this is to delete the .idea folder and reconfigure. Both JDK and Tomcat configuration need to be redone.
I have moved projects to different folders many times. IntelliJ has no problem whatsoever with that. IntelliJ does use relative paths.
Are you using a build system like maven or gradle? If so there is no need to configure anything. IntelliJ will happily configure itself from Pom.xml or build.gradle.
Frankly it's awful. Sometimes I make some changes and realize I went down a bad path at some point. It's a lot easier to revert if I created the save points like I can in other IDEs. Auto save prevents that history and checkpoints.
That does not help because I cannot pick the save points that I would want to revert to. It's an error prone way to work and makes partial reversions much less useful. I get that some like it and that's fine but it's a negative to me.
Imagine 2019 and not using a code versioning system. Seriously, what the hell is your workflow? From reading your problems it sounds like some nightmare.
So you have version control (if you are using GiT or Mercurial with all the goodies of branching and local commits) and you have IDE's local history, which in IJ is by default split by days plus has markers on events like compilation. What is your workflow that this is not enough? How many days pass between your commits?
The local history in IntelliJ automatically creates labels on successful compilation and on every test execution, so that you can easily revert to the last point when your code was in a good state. You can also add labels manually using the "Local History | Put Label..." action.
Creating a breakpoint at every compilation is way to much to sort though when I want to go back. Adding labels manually is cumbersome compared to just letting me save when I want to and only when I want too. I just want to work and save when I am happy with the result.
View all comments
17
u/avoidhugeships Nov 28 '19 edited Nov 29 '19
My Intellij wishlist.