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

Fix #10321 to avoid multiple warnings about skipped deployment due to missing / unsupported environment #10438

Closed

Conversation

sbordet
Copy link
Contributor

@sbordet sbordet commented Aug 30, 2023

The warning message was causing confusion in case of multiple deployers. See also #10437.

The warning message was causing confusion in case of multiple deployers.
See also #10437.

Signed-off-by: Simone Bordet <[email protected]>
@sbordet sbordet requested review from gregw, joakime and janbartel August 30, 2023 10:46
Copy link
Contributor

@joakime joakime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see this as a partial fix.

Yes, having this warning show up multiple times is a mistake.
But the purpose of the warning should still be present, somehow, perhaps in the right place.

Example scenario:

  1. Jetty Base created with --add-module=deploy (or just core-deploy, but not ee10-deploy)
  2. A EE10 war file is copied into ${jetty.base}/webapps/
  3. Start Jetty.

That warning is the only thing telling the user that this webapp cannot be deployed, because there is no environment for it.

We still need that warning, but in the right place.
Without that warning the deploy silently fails.

@joakime joakime changed the title Reverted #10321. Fix #10321 to avoid multiple warnings about skipped deployment due to missing / unsupported environment Aug 30, 2023
@sbordet
Copy link
Contributor Author

sbordet commented Aug 30, 2023

Closing this as the warning it is better to keep the warning in the common case of deploying 1 webapp with the wrong deployer.

@sbordet sbordet closed this Aug 30, 2023
@gregw
Copy link
Contributor

gregw commented Aug 30, 2023

Not that it is not just duplicates, but false positives.

@olamy olamy deleted the fix/jetty-12-10321-revert-warn-if-no-env branch September 5, 2023 00:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants