# Dependency substitutions with classifiers

**URL:** <https://discuss.gradle.org/t/dependency-substitutions-with-classifiers/22481>\
**Category:** Help/Discuss\
**Created:** [April 27, 2017, 8:27pm UTC](https://discuss.gradle.org/t/dependency-substitutions-with-classifiers/22481 "2017-04-27T20:27:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfriedman](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@jfriedman](https://discuss.gradle.org/u/jfriedman)\
**Post date:** [April 27, 2017, 8:27pm UTC](https://discuss.gradle.org/t/dependency-substitutions-with-classifiers/22481/1 "2017-04-27T20:27:06Z")

</div>

We have a need to run dependency substitutions between project and module, where the module/jar file has a classifier and the project jar is identified by a configuration.

The boilerplate dependency substitution does not support either of these.

It is possible to programmatically check for a project being present, and declare a module dependency with classifier if it is not - but gradle does not allow programmatically declaring a project dependency including configuration when the project is present.

Has anyone found a path through this conundrum that works? Is gradle planning on supporting this kind of thing in the near future?

thank you for any help