-
Notifications
You must be signed in to change notification settings - Fork 261
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
Stewardship engine services - no Jar #3330
Comments
The server module does have code - I'll add some stub code to the others so these warnings go away. I would like to get back to the stewardship services soon and would rather keep them moving forward |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions. |
Module deleted |
Stewardship engine services currently have no code, and are producing empty jars.
This causes both a build warning, as well as release errors due to the invalid artifact.
We introduced this a few releases ago, if we don't yet have modules to build I suggest we stop building them by commenting out the submodules, or we make them compliant. otherwise we end up chasing errors in the build and release process unnecessarily.
The text was updated successfully, but these errors were encountered: