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
See here, and the linked issue for details and background. This blog post is also helpful, specifically for library maintainers.
In each module in this project, we should add this maven step (we could also add it in the parent POM and somehow grab the name dynamically). We should be careful that the module name matches the "highest level" package in the module.
The text was updated successfully, but these errors were encountered:
We should be able to utilize existing POM properties to derive unique names and make it a recommendation to add this to POM. And naming could be recommended to derive from existing values. For example,
See here, and the linked issue for details and background. This blog post is also helpful, specifically for library maintainers.
In each module in this project, we should add this maven step (we could also add it in the parent POM and somehow grab the name dynamically). We should be careful that the module name matches the "highest level" package in the module.
The text was updated successfully, but these errors were encountered: