Hi Peter, Thank you for answering my questions.
I can try list few things about having two output folder that’s user unfriendly to me.
- The default “bin” directory is not ideal to use as a folder for generated class files. Many project use “bin” to store executable scripts that they add into source control. Default output here means harder to clean, or you need filter to diff which one is generate vs which one you actually want.
We sure can change the Eclipse’s “bin” to some where else, but that’s the original point of this post, why not default to more user friendly output folder?
-
With two folder output, now we need to add extra entry into ignore file to source control so to ignore eclipse output folder.
-
With two folders, now “gradle clean” is not clean because it won’t delete the bin generated files. If we must use two separate folder, I rather it be under “build/eclipse”. Seems more manageable.
-
For project that has script to load “build/classes” during development as classpath, now they also need
to add “bin”, but then they would need to know which one has the latest compiled classes or else they are staled.
- I usually develop on IDE, and let gradle run in CI. Of course I do command line build too, but hardly while I am still editing files with Eclipse together. So separating two class output folder doesn’t make sense to me.
All these comes because there two output generated folders to deal with. Obviously I have no knowledge of how gradle compiler vs Eclipse compiler work, but it just seems hard to manage.
Again, I dont’ mean to be picky or rude. I just want to give you feedback.