[GRADLE-2381] `gradle dependencies` output swallows classifier tags Created: 11/Jul/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


Hi. I am having problems with gradle ignoring my classifier: 'tests'. Here is the build script:

apply plugin: 'java'


{ mavenCentral() }


{ //compile group: 'org.neo4j', name: 'neo4j-kernel', version: '1.8.M05' testCompile group: 'org.neo4j', name: 'neo4j-kernel', version: '1.8.M05', classifier: 'tests' }

And here the output of the 'dependencies' task (trimmed to test-related):
testCompile - Classpath for compiling the test sources.
--- org.neo4j:neo4j-kernel:1.8.M05 [default]
--- org.apache.geronimo.specs:geronimo-jta_1.1_spec:1.1.1 [compile,master,runtime]

testRuntime - Classpath for running the compiled test classes.
--- org.neo4j:neo4j-kernel:1.8.M05 [default]
--- org.apache.geronimo.specs:geronimo-jta_1.1_spec:1.1.1 [compile,master,runtime]

As you see, it depends on the neo4j artifact without the classifier, which is wrong in this case. The jar file in maven central exists ;d and has this URL:

I am using gradle 1.0.

How to express a testCompile dependency on a test jar?

[1] http://search.maven.org/remotecontent?filepath=org/neo4j/neo4j-kernel/1.8.M05/neo4j-kernel-1.8.M05-tests.jar

Comment by Gradle Forums [ 11/Jul/12 ]

I think it's just a(nother) limitation of the `gradle dependencies` output. If you print out the files on the `testCompile` configuration, you'll see that `neo4j-kernel-1.8.M05-tests.jar` is present.

PS: Please use HTML code tags for all code and other output.

Comment by Gradle Forums [ 11/Jul/12 ]

Sorry about the code tags.

Ok, I just ignored the errors of my IDEA and wrote the code, and it does compile and run fine, thanks for the tip. Should a bug be issued for that? This should probably be fixed, as it is really confusing.
Now it's time to ask the IntelliJ guys why IDEA is not comfortable with classifiers - maybe they are using the output of dependencies somehow?

Comment by Gradle Forums [ 11/Jul/12 ]

Not sure. I recommend to file an IDEA issue.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:20:22 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.