You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run a normal JVM process (using TestRunner main class) when executing tests in YAKS S2i image. Need to change this to a Maven build in order to support dependency resolving mechanisms. This is mandatory when using components in tests that are not baked into the YAKS Docker image.
This helps us to support additional runtime dependencies that we need to add to the YAKS runtime. For instance when the test uses a camel component that is not part of the default YAKS runtime we want to automatically download the artifacts and transitive dependencies at runtime.
The text was updated successfully, but these errors were encountered:
Switching YAKS runtime to Maven instead of running plain JVM jar for executing tests. This enables us to use Maven dependency resolving for additional components used in tests.
- Refactor YAKS Docker image to use Maven build instead of jar execution
- Add local m2 repository to YAKS Docker image holding all dependencies and required plugins to run a test
- Tidy up Maven dependencies and dependency management
- Move TestReporter to yaks-testing-standard module
- Refactor yaks-testing module to represent the new YAKS runtime using Maven
We run a normal JVM process (using TestRunner main class) when executing tests in YAKS S2i image. Need to change this to a Maven build in order to support dependency resolving mechanisms. This is mandatory when using components in tests that are not baked into the YAKS Docker image.
This helps us to support additional runtime dependencies that we need to add to the YAKS runtime. For instance when the test uses a camel component that is not part of the default YAKS runtime we want to automatically download the artifacts and transitive dependencies at runtime.
The text was updated successfully, but these errors were encountered: