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

Project micronaut-core:inject-kotlin: priming build fails with null message #6537

Closed
MartinBalin opened this issue Oct 5, 2023 · 0 comments · Fixed by #6548
Closed

Project micronaut-core:inject-kotlin: priming build fails with null message #6537

MartinBalin opened this issue Oct 5, 2023 · 0 comments · Fixed by #6548
Assignees
Labels
Gradle [ci] enable "build tools" tests kind:bug Bug report or fix VSCode Extension [ci] enable VSCode Extension tests

Comments

@MartinBalin
Copy link
Contributor

Apache NetBeans version

Apache NetBeans 19

What happened

Open micronaut-core v4.1.x using VSNetBeans 19.0.301 Graalvm 23 JDK17.
Following dialog is shown during project opening:
Project micronaut-core:inject-kotlin: Priming Build Required.: In order to be able to read this project, NetBeans needs to execute its Gradle scripts as priming build. Executing Gradle scripts allows arbitrary code execution, as current user, on this system. click OK to run Priming build.
and then also for project micronaut-core:test-suite-kotlin-ksp also click OK to priming build it.
It then ends with following error message:
Priming build failed for Project micronaut-core:inject-kotlin: NULL and same for Priming build failed for Project micronaut-core:test-suite-kotlin-ksp: NULL
Does not seem to do any harm to project editing. Tried code completion, tests run, go to definition,...

How to reproduce

No response

Did this work correctly in an earlier version?

Apache NetBeans 18

Operating System

macOS 13.3.1 (a)

JDK

Graalvm 23 JDK17

Apache NetBeans packaging

Apache VSNetBeans for VSCode

Anything else

No response

Are you willing to submit a pull request?

No

@MartinBalin MartinBalin added kind:bug Bug report or fix needs:triage Requires attention from one of the committers labels Oct 5, 2023
@MartinBalin MartinBalin added VSCode Extension [ci] enable VSCode Extension tests and removed needs:triage Requires attention from one of the committers labels Oct 5, 2023
@sdedic sdedic added the Gradle [ci] enable "build tools" tests label Oct 9, 2023
sdedic added a commit to sdedic/incubator-netbeans that referenced this issue Oct 9, 2023
sdedic added a commit that referenced this issue Oct 16, 2023
…flow

#6536, #6537: avoid stack overflow, catch missing artifacts to be downloaded.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Gradle [ci] enable "build tools" tests kind:bug Bug report or fix VSCode Extension [ci] enable VSCode Extension tests
Projects
None yet
2 participants