[GRADLE-688] Project dependency in a compile configuration should use the classes dir of the target project, rather than the jar Created: 09/Oct/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Won't Fix Votes: 3

Issue Links:
Related to GRADLE-687 Project dependency on a war project i... Resolved


This is to avoid generating a jar file when we don't necessarily need it

Comment by Thomas Glaeser [ 05/Mar/10 ]

Hans - I was wondering if this could be added to one of the next 0.9 builds as I'm in desperate need of a solution for this issue.

I also think that it should rather be implemented at the AbstractArchiveTask level and not for jars only.

In my situation, which is kind of an legacy Java application, we produce a resulting zip artifact which has a code/classes directory containing the Java packages that are required by a dependent project. The zip artifact also contains a code/jars directory containing jar archives that should be added to the archive configuration as well. So it is very similar to the more standardized war bundling.

What about if we don't have a project dependency to this type of artifact but a dependency to the artifact itself after uploading it into the repository?

It probably doesn't make a difference, but we have written our own plugins and tasks and would need to access this functionality from within there only, not from the build.gradle.

Comment by Hans Dockter [ 17/Apr/10 ]

Have you made any progress in addressing your problem? I think there are a couple of ways you could solve your specific problem with the current capabilities of Gradle.

Comment by Thomas Glaeser [ 19/Apr/10 ]

Nope. That's a critical issue for us to use Gradle for our projects. I was hoping to find the time soon to further look into it in order to propose a solution. I'm not aware of any current Gradle features that could possibly address the issue. Any suggestions are highly appreciated. Thanks.

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 11:36:18 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.