microsoft / microsoft/vscode-java-pack

add apply plugin: "net.serenity-bdd.serenity-gradle-plugin" to build.gradle, then vscode is not able to recognize the project as a java project

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

Nobody has claimed this yet.

ai-triaged bug
Dominant language
TypeScript
Stars
352
Forks
166
Avg merge
17h 47m
Merged PRs (30d)
32

Description

adding apply plugin: "net.serenity-bdd.serenity-gradle-plugin" to build.gradle, then vscode is not able to recognize the project as a java project

Environment:

  • VS Code Version: 1.85.1
  • Extension Version: Extension Pack for Java v0.25.15
  • JDK Type & Version: Oracle, v11.0.8
  • OS Type & Version: windows

Step to Reproduce:

  1. Have a standard alone java starter gradle project, e.g. we use spring gradle sample java project from https://github.com/spring-guides/gs-gradle, download the project to local machine, and upgrade gradle to version 8.2.1
  2. using vscode open folder complete of the project
  3. at this point, we can run gradle build of the project, vscode recognize this project as a java project, and shows all objects and libs info in tab "JAVA PROJECTS"
  4. now open build.gradle file and add the following plugin:
    plugins {
    id "net.serenity-bdd.serenity-gradle-plugin" version "4.0.30"
    }
  5. run ./gradlew clean build
  6. right click tab "JAVA PROJECTS" and select "clean workspace"
  7. wait for vscode clean workspace is done, you will see below message under tab "JAVA PROJECTS"
    No java projects found in the current workspace. you can open a java project folder......

Expected Behavior:
at step 7. we should see the updated java objects and libs information under tab "JAVA PROJECTS"

Actual Behavior:
vscode does not recognize the java project any more and you will see below message under tab "JAVA PROJECTS"
No java projects found in the current workspace. you can open a java project folder......

Related Issues:
No

vscode-java-project-error-screen
build.gradle.txt

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the issue with the spring-guides gs-gradle project, Gradle 8.2.1, VS Code, and the Serenity Gradle plugin in build.gradle. Start by comparing Java Projects before and after running clean build and Clean Workspace; done means the project and its Java objects and libraries remain recognized after the plugin is added.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, vscode
Domain
developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.