Skip to content
SmallRye Build

add support for @ApplyGuard configuration #1866

Sign in to view logs

add support for @ApplyGuard configuration

add support for @ApplyGuard configuration #1866

You are viewing an older attempt in the history of this workflow run. View latest attempt.
Triggered via pull request January 14, 2025 14:51
@LadicekLadicek
opened #1105
Ladicek:config-for-applyguard
Status Cancelled
Total duration 1h 5m 20s
Artifacts –

build.yml

on: pull_request
Matrix: build
Quality
0s
Quality
Fit to window
Zoom out
Zoom in

Annotations

34 errors and 5 warnings
Build with JDK 24-ea (macos-latest)
Process completed with exit code 1.
Build with JDK 17 (macos-latest)
Process completed with exit code 1.
Build with JDK 17 (windows-latest)
[QualifierInstance {annotationClass=interface jakarta.enterprise.inject.Default, values={}}]
Build with JDK 17 (windows-latest)
No active contexts for scope type jakarta.enterprise.context.ApplicationScoped
Build with JDK 17 (windows-latest)
No active contexts for scope type jakarta.enterprise.context.ApplicationScoped
Build with JDK 23 (windows-latest)
Unable to access CDI
Build with JDK 23 (windows-latest)
Unable to access CDI
Build with JDK 23 (windows-latest)
Unable to access CDI
Build with JDK 23 (windows-latest)
Unable to access CDI
Build with JDK 11 (windows-latest)
Unable to access CDI
Build with JDK 11 (windows-latest)
No active contexts for scope type jakarta.inject.Singleton
Build with JDK 11 (windows-latest)
No active contexts for scope type jakarta.enterprise.context.ApplicationScoped
Build with JDK 11 (windows-latest)
No active contexts for scope type jakarta.enterprise.context.ApplicationScoped
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 24-ea (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
The run was canceled by @Ladicek.
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (windows-latest)
Unable to access CDI
Build with JDK 21 (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build with JDK 24-ea (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build with JDK 17 (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build with JDK 23 (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build with JDK 11 (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636