redhat-developer / redhat-developer/vscode-java

auto generated prefs

Open
#1,882 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

[provide a description of the issue]
Every time command Java: Update Project is called few prefs are added by default to

  • org.eclipse.jdt.apt.core.prefs:
    org.eclipse.jdt.apt.genTestSrcDir=target/generated-test-sources/test-annotations
  • org.eclipse.jdt.core.prefs
    org.eclipse.jdt.core.compiler.problem.enablePreviewFeatures=disabled
    org.eclipse.jdt.core.compiler.problem.reportPreviewFeatures=ignore
    org.eclipse.jdt.core.compiler.release=disable

Is it possible to disable this? In current repository that I am working on I can't modify those files, so I would like to keep them without modification or at least change path where I can specifically update and gitignore them.
I tried copping them to .vscode/ folder with no luck. New option java.settings.url to point custom pref settings with those options also didn’t work.

Any adviced what I could try or what I did wrong?

Environment
  • Operating System:
  • JDK version: JDK 11.0.1 or OpenJDK-15.0.2 (same behavior)
  • Visual Studio Code version: 1.55.2
  • Java extension version: 0.77.0
Steps To Reproduce
  1. Files org.eclipse.jdt.apt.core.prefs and org.eclipse.jdt.core.prefs have no mentioned options
  2. Run command Java: Update Project
  3. Files org.eclipse.jdt.apt.core.prefs and org.eclipse.jdt.core.prefs were automatically updated

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the Java: Update Project command and how it updates org.eclipse.jdt.apt.core.prefs and org.eclipse.jdt.core.prefs. Reproduce with the listed JDK, VS Code, and extension versions, then determine whether these preference changes can be disabled or redirected without modifying repository files; done means unwanted changes no longer occur or a supported setting is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.