Feature Request: configurable `defaultOutputDir` instead of hardcoded `bin`

Feature Request

Please provide a configuration to change defaultOutputDir bin

Detail

I’m not an eclipse user, as I know, bin is widely used as a dir that stores shell scripts, but vscode java plugin uses it as the default output dir, and can not be changed by configuration, the only way I know is using gradle eclipse plugin to generate .classpath with modified config by groovy script in build.gradle, see #634

buildDir = "build/gradle"
apply plugin: 'java'
apply plugin: 'eclipse'
eclipse {
  classpath {
    defaultOutputDir = file('build/eclipse')
    file.whenMerged {
      entries.each { entry ->
        if (entry.kind == 'src' && entry.hasProperty('output')) {
          entry.output = entry.output.replace('bin/', "build/eclipse/")
        }
      }
    }
  }
}

@jdneo https://github.com/redhat-developer/vscode-java/issues/2801#issuecomment-1318256946

You can vote for https://github.com/redhat-developer/vscode-java/issues/1615 to help us prioritize.

If anyone encounter this issue, please comment / give 👍 / link related issue to this one, to help the team escalate the priority of this issue.

[jdneo]

@n-peugnet The newest Language support for Java extension adds a new setting to set the output path for project without any build tools.

java.project.outputPath: A relative path to the workspace where stores the compiled output. Only effective in the WORKSPACE scope. The setting will NOT affect Maven or Gradle project.

@pan3793 Sorry currently there is no plan to make that setting be able to impact Maven/Gradle project. But we will keep an eye on this request.

[gardner]

I onboard people at work. This issue confuses people and ultimately causes people to uninstall the extension.