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
Dependencies may be inclusions or requirements. Requirements should not be exposed in the public API of a project. Only inclusions affect the build hash of a phase; changing a requirement shouldn't change the hash of downstream projects. Requirements can be shaded with Umbrageous automatically, and hence, different versions can coexist on the same classpath.
Conversely, if a project's dependencies contain two non-equal inclusions, then these must be resolved.
If a dependency is both an inclusion and a requirement, then it should be treated as an inclusion.
The text was updated successfully, but these errors were encountered:
Dependencies may be inclusions or requirements. Requirements should not be exposed in the public API of a project. Only inclusions affect the build hash of a phase; changing a requirement shouldn't change the hash of downstream projects. Requirements can be shaded with Umbrageous automatically, and hence, different versions can coexist on the same classpath.
Conversely, if a project's dependencies contain two non-equal inclusions, then these must be resolved.
If a dependency is both an inclusion and a requirement, then it should be treated as an inclusion.
The text was updated successfully, but these errors were encountered: