Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestJars support #1197

Closed
BoykoAlex opened this issue Feb 23, 2024 · 3 comments
Closed

TestJars support #1197

BoykoAlex opened this issue Feb 23, 2024 · 3 comments
Labels
for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: testjars-support type: enhancement

Comments

@BoykoAlex
Copy link
Contributor

The idea is to make the app having TestJars on the classpath launched via the IDE aware of GAVs, classpath and main classes of projects residing in the same workspace. Thus TestJar support won't attempt to load these projects from maven but instead use workspace versions of these.
See spring-projects-experimental/spring-boot-testjars#15 for more details

@martinlippert martinlippert added for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: testjars-support and removed status: waiting-for-triage labels Feb 26, 2024
@martinlippert martinlippert added this to the 4.22.1.RELEASE milestone Feb 26, 2024
@BoykoAlex
Copy link
Contributor Author

The plan is the following:

  1. Launch creation is initiated on the IDE client side.
  2. IDE client executes a command on the LS side to receive a list of "Executable" Boot Projects where ExecutableBootProject looks like:
interface ExecutableBootProject {
  name: string;
  uri: string;
  bootAppClass: string;
  classpath: string[]
  gav: string; // <groupId>:<artifactId>:<version>
}

The data is available on the LS in memory hence should be rather fast to arrive
3. Client saves this data in property files somewhere (temp folder? workspace folder?)
4. Updates launch with TestJar needed environment variables. (Would be nice if we could avoid saving into files... seems somewhat redundant. Perhaps it can be packed into 2 environment variables...)

@BoykoAlex
Copy link
Contributor Author

TestJars support is for maven projects only so far: 52dd4d2

@BoykoAlex
Copy link
Contributor Author

Preference setting went in with d3af0a3.
Gradle projects GAV and hence the TestJars support to be delivered with #1201 in 4.22.1. The rest is done for 4.22.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: testjars-support type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants