| Re: [aether-users] filtering artifacts |
Igor Fedorenko wrote:
Somewhat related. Can you explain the reason why some filter/transform callbacks are at system session level, while other, DependencyFilter in particular, are at request level?
Based on usage patterns seen with Maven, the intent is to put hooks that are usually applicable to many requests on the session, and have the *Request focus on settings which tend to be specific for a given call.
As a concrete example, the ordinary Maven plugin has no need to change any of the session level config (e.g. graph construction is always the same as per Maven core rules) and can just pass this along as is, allowing the plugin to concentrate on filling out the relevant options for the request (e.g. what scopes to resolve) and not get overwhelmed by the API.
In the end, both session and request carry settings/callbacks that affect the call. The current separation between those is an attempt of making the myriad of options easier to grasp for the common case.
Benjamin