<commit_before>This feature is really a bucket for key things we want to fix in the short-term for Dependency Management, many of which have require
(or have the potential for) a strategic solution.

As this 'feature' is a list of bug fixes, this feature spec will not follow the usual template.

# Lastest status dynamic versions work across multiple repositories

See [GRADLE-2502](http://issues.gradle.org/browse/GRADLE-2502)

### Test coverage

1. Using `latest.integration`
    1. Empty repository fails with not found.<commit_msg>Added stories for fixes to GRADLE-2752 and GRADLE-2516<commit_after>This feature is really a bucket for key things we want to fix in the short-term for Dependency Management, many of which have require
(or have the potential for) a strategic solution.

As this 'feature' is a list of bug fixes, this feature spec will not follow the usual template.

# Conflict resolution considers conflicts on production classes

See [this post](http://forums.gradle.org/gradle/topics/npe_in_dependencygraphbuilder_dependencyedge_getfailure)
See [GRADLE-2752](http://issues.gradle.org/browse/GRADLE-2752)

- Allow self-resolving dependencies to imply zero or more module versions.
- Change the resolution algorithm to consider this during conflict resolution. Self-resolving dependencies cannot be evicted and must
  always be selected. Assert that the self-resolving dependency is compatible-with the requested version. Fail resolution if not.
- Change the Java plugin to attach current project's identifier to the main and test classes.
    - To infer the identifier of the current project.
        - Identifier of any publication.
        - Project (group, name, version).
        - Maven deployer.
        - Project (group, archivesBaseName, version).
- Change the resolution algorithm so that the root node is not considered by conflict resolution.

TBD - A later story should travel back from each publication to determine if the main or test binary is included in the publication.
Use this publication's identifier if so.

# Conflict resolution considers local dependencies

See [GRADLE-2516](http://issues.gradle.org/browse/GRADLE-2516)

- Change the local dependencies (eg `gradleApi()`, `localGroovy()`) to imply the various modules that they contribute to the result.

# Lastest status dynamic versions work across multiple repositories

See [GRADLE-2502](http://issues.gradle.org/browse/GRADLE-2502)

### Test coverage

1. Using `latest.integration`
    1. Empty repository fails with not found.
{'fraction_non_alphanumeric': 0.06447784810126582, 'fraction_numerical': 0.01740506329113924, 'mean_word_length': 4.30188679245283, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3740190', 'n_tokens_mistral': 686, 'n_tokens_neox': 633, 'n_words': 313}