[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-276) Gradle resolver doesn't support custom configurations
Andreas Klemp created SHRINKRES-276:
---------------------------------------
Summary: Gradle resolver doesn't support custom configurations
Key: SHRINKRES-276
URL: https://issues.jboss.org/browse/SHRINKRES-276
Project: ShrinkWrap Resolvers
Issue Type: Feature Request
Components: gradle
Affects Versions: 3.0.0-beta-2
Environment: Windows 7, Gradle 3.4, Eclipse Mars
Reporter: Andreas Klemp
Having a gradle project with additional source set and configurations, the Gradle resolver
does not pickup the dependencies in the new configurations.
build.gradle snippet:
{code}
sourceSets {
integrationTest {
java {
compileClasspath += main.output
runtimeClasspath += main.output
srcDir file('src/integrationTest/java')
}
resources.srcDir file('src/integrationTest/resources')
}
}
configurations {
integrationTestCompile.extendsFrom compile
integrationTestRuntime.extendsFrom runtime
}
dependencies {
integrationTestCompile group: 'org.slf4j', name: 'slf4j-api', version:
'1.7.7'
integrationTestImplementation group: 'org.slf4j', name: 'slf4j-api',
version: '1.7.7'
}
{code}
No matter which of the new configurations is used, the dependecy is not resolved when
searching all scopes:
{code}
Gradle.resolver()
.forProjectDirectory(".")
.importDependencies(ScopeType.values())
.resolve()
.asList(JavaArchive.class)
.stream()
.filter(a -> a.getName().contains("slf4j"))
.forEach(System.out::println);
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)