Skip to content

Actions: redhat-developer/vscode-java

Actions

Potential Duplicate Issues

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
duplicate-issues-detector.yaml
139 workflow run results
139 workflow run results

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Error upon importing project Potential Duplicate Issues #1024: Issue #3853 edited by mamilic
10s
10s
Symbol lookup in Java shows duplicates Potential Duplicate Issues #1023: Issue #3854 opened by rajinder-yadav
11s
11s
Error upon importing project Potential Duplicate Issues #1022: Issue #3853 opened by mamilic
10s
10s
Performance - TTFI for Reopening Previously Imported Java Projects in VS Code Potential Duplicate Issues #1021: Issue #3852 opened by mamilic
11s
11s
Can not autocomplete/find inner class Potential Duplicate Issues #1020: Issue #3815 edited by rgrunber
10s
10s
Peek/Go To Implementations points to method with same name Potential Duplicate Issues #1019: Issue #3823 edited by rgrunber
11s
11s
Peek References show to the current selected one Potential Duplicate Issues #1018: Issue #3850 edited by mamilic
14s
14s
Peek References show to the current selected one Potential Duplicate Issues #1017: Issue #3850 opened by mamilic
14s
14s
cannot read lifecycle mapping metatdata when opening a java project in vscode Potential Duplicate Issues #1016: Issue #3839 edited by ldh-iwnl
12s
12s
Focus on Newly Created Method/Class in "Create Method" Quick Fix Potential Duplicate Issues #1015: Issue #3844 opened by mamilic
11s
11s
MapStruct mapper generation error after upgrading to 1.36 Potential Duplicate Issues #1014: Issue #3843 opened by nicolasriousset
11s
11s
cannot read lifecycle mapping metatdata when opening a java project in vscode Potential Duplicate Issues #1013: Issue #3839 edited by ldh-iwnl
11s
11s
cannot read lifecycle mapping metatdata when opening a java project in vscode Potential Duplicate Issues #1012: Issue #3839 edited by ldh-iwnl
13s
13s
cannot read lifecycle mapping metatdata when opening a java project in vscode Potential Duplicate Issues #1011: Issue #3839 edited by ldh-iwnl
14s
14s
cannot read lifecycle mapping metatdata when opening a java project in vscode Potential Duplicate Issues #1010: Issue #3839 edited by ldh-iwnl
10s
10s
After upgrade version >1.35, my project with lombok and hibernate-jpamodelgen stop to works Potential Duplicate Issues #1009: Issue #3842 edited by AntonioSeleda
10s
10s
After upgrade version >1.35, my project with lombok and hibernate-jpamodelgen stop to works Potential Duplicate Issues #1008: Issue #3842 edited by AntonioSeleda
10s
10s
After upgrade version >1.35, my project with lombok and hibernate-jpamodelgen stop to works Potential Duplicate Issues #1007: Issue #3842 opened by AntonioSeleda
12s
12s
High CPU Usage Potential Duplicate Issues #1006: Issue #3841 opened by tonyrusignuolo
15s
15s
VS Code is Showing Errors which doesn't Exist after 1.36.0 Update Potential Duplicate Issues #1005: Issue #3840 opened by mnurfath
13s
13s
cannot read lifecycle mapping metatdata when opening a java project in vscode Potential Duplicate Issues #1004: Issue #3839 edited by ldh-iwnl
10s
10s
cannot read lifecycle mapping metatdata when opening a java project in vscode Potential Duplicate Issues #1003: Issue #3839 opened by ldh-iwnl
11s
11s
After ./mvnw clean package, the java file generated in the output directory target is re-identified as a project file by the vscode-java plugin. Potential Duplicate Issues #1002: Issue #3838 edited by mozhuanzuojing
9s
9s
After ./mvnw clean package, the java file generated in the output directory target is re-identified as a project file by the vscode-java plugin. Potential Duplicate Issues #1001: Issue #3838 edited by mozhuanzuojing
10s
10s
After ./mvnw clean package, the java file generated in the output directory target is re-identified as a project file by the vscode-java plugin. Potential Duplicate Issues #1000: Issue #3838 edited by mozhuanzuojing
11s
11s