-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Use webapp artifacts for examples and tests #2992
Milestone
Comments
@olamy this feels like something you could tackle? |
@gregw yup for sure. |
starting working on it and found few examples broken/not maintained :) |
depends on #3138 |
This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions. |
definitely todo |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Lots of tests and examples are using relative paths to find webapps and keystores to run/test against. Examples include:
This is fragile and dependent on working directory, IDEs etc.
Instead, we should import webapps as maven artifacts and install them in a known location in target.
The text was updated successfully, but these errors were encountered: