[GRADLEREV-60] PluginResolver doesn't need to be named Created: 02/Jan/14  Updated: 02/Jan/14  Resolved: 02/Jan/14

Status: Resolved
Project: Gradle Code Review Tasks
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Luke Daley Assignee: Luke Daley
Resolution: Fixed Votes: 0
Labels: None


There will need to be two things pieces for each resolver:

1. Some DSL model object that defines the configuration for a particular plugin repository.
2. A resolver service implementation that does the work of resolving plugins from that repository.

The build author does stuff with the DSL object, which is then later converted into a service implementation when we need the result.

The DSL object can extend Named, but should not have a resolve() method. The resolver service can have a resolve() method, but should not extend Named.

So, given that this interface later turns into the service interface, let's get rid of Named from here.

Generated at Wed Jun 30 11:19:23 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.