-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Clean up split packages between deployment and run time artifacts #44710
Comments
The recommended strategy is:
I would also suggest that private packages be named |
Let's not go too far with this, please. The current rules are:
Let's first see if we can fix the issues just by respecting these simple rules that have been there since the start. Also, we don't need to duplicate the classes if they are not user-facing APIs (except if we have a build item that is used by everyone for instance). We can have some level of breakage. And then we can have deeper discussion as part of the WG as to what is the target in the future and make sure we follow it. But I don't want to have the discussion now that we are time-constrained to get the issues fixed. |
Sure, that's completely in line with my suggestion. As long as we have a convention that is consistent then we're in agreement. |
Here's the script I used to find the split packages. Notably, this doesn't cover integration tests, which add a large number of additional split package issues. https://gist.github.com/dmlloyd/4963077077c4757da6d4481e55c87841 |
There are several instances of extensions which split packages across more than one artifact. Each individual problem will be opened as a sub-issue.
External related issues:
org.aesh.readline
aeshell/aesh#349The text was updated successfully, but these errors were encountered: