IntegrationTest has wrong classpath order

Open
#81 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
groovy

Research direction

Start by locating the IntegrationTest source-set and runtimeClasspath configuration, then use the showClassPathTest() task from the issue to reproduce the ordering. Done means integTest, test, and main classes/resources appear before the jars, matching the expected result.

Written by the indexing model from the issue text.

Description

Integration test apply wrong classpath order and as result class shadowing isn't work.

task showClassPathTest() {
	doLast {
		sourceSets.integTest.runtimeClasspath.each { println it}
	}
}

Result:

/.../build/classes/java/integTest
/.../build/resources/integTest
...
jars
...
/.../build/classes/java/test
/.../build/resources/test
/.../build/classes/java/main
/.../build/resources/main

And expected result:

/.../build/classes/java/integTest
/.../build/resources/integTest
/.../build/classes/java/test
/.../build/resources/test
/.../build/classes/java/main
/.../build/resources/main
...
jars
...
Dominant language
Groovy
Stars
98
Forks
19
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nebula-plugins/nebula-project-plugin

All issues in nebula-plugins/nebula-project-plugin

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.