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

Compilation is broken on main #20591

Closed
gemmellr opened this issue Oct 7, 2021 · 2 comments · Fixed by #20592
Closed

Compilation is broken on main #20591

gemmellr opened this issue Oct 7, 2021 · 2 comments · Fixed by #20592
Labels
kind/bug Something isn't working
Milestone

Comments

@gemmellr
Copy link
Contributor

gemmellr commented Oct 7, 2021

Describe the bug

The main branch fails to compile as of 99a4d06

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1-jboss-2:compile (default-compile) on project quarkus-core-deployment: Compilation failure: Compilation failure: 
[ERROR] /path.to/quarkus/core/deployment/src/main/java/io/quarkus/deployment/pkg/steps/NativeImageBuildStep.java:[610,25] cannot find symbol
[ERROR]   symbol:   variable isContainerBuild
[ERROR]   location: class io.quarkus.deployment.pkg.steps.NativeImageBuildStep.NativeImageInvokerInfo.Builder
[ERROR] /path.to/workspace/quarkus/core/deployment/src/main/java/io/quarkus/deployment/pkg/steps/NativeImageBuildStep.java:[610,24] illegal parenthesized expression

Expected behavior

It compiles.

Actual behavior

It doesnt compile.

How to Reproduce?

mvn clean install -DskipTests

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@gemmellr gemmellr added the kind/bug Something isn't working label Oct 7, 2021
@gemmellr
Copy link
Contributor Author

gemmellr commented Oct 7, 2021

May be character assassination, but speculating wildly... it looks like the file in question was just changed in #20451 in a similar-looking area.

@zakkak @geoand ^

@geoand
Copy link
Contributor

geoand commented Oct 7, 2021

I am aware, thanks.

I will push a fix ASAP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants