[GRADLE-171] Introduce Configuration object to our domain Created: 30/Jul/08 Updated: 04/Jan/13 Resolved: 06/Nov/08 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.2 |
| Fix Version/s: | 0.5 |
| Type: | Improvement | ||
| Reporter: | Hans Dockter | Assignee: | Adam Murdoch |
| Resolution: | Fixed | Votes: | 0 |
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
From Adam Murdoch: There are a number of methods on DependencyManager which take a configuration name as their first parameter, or return a map indexed by configuration name. This suggests a missing domain object, which would represent a configuration and which could be used to configure, query, resolve and publish the configuration (I'm not referring to ivy's Configuration object here, though we would end up converting each configuration to one of these). I think it would be good to have a strong domain model for the things which the build produces, not just how it produces them. |
| Comments |
| Comment by Hans Dockter [ 08/Oct/08 ] |
|
It would be good if we had a nicer way to include the artifacts from a configuration in an archive which dealt with the above issues. For example, if we had a Configuration domain object and it implemented FileCollection, you could just add the configuration object to the archive. |
| Comment by Hans Dockter [ 22/Oct/08 ] |
|
Should we close this and file new issues for improvements? |
| Comment by Adam Murdoch [ 22/Oct/08 ] |
|
Yes, probably. I need to write up some stuff in the user guide about this |
| Comment by Adam Murdoch [ 06/Nov/08 ] |
|
This is good enough for a first cut. |