[GRADLE-1024] Documentation example is not working Created: 08/Jul/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Andrew Schetinin Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

The example is not useful - I tried copying it and it did not work because it did not find spiJar property, and there is not a clue of what that property should be.
After changing the dependency to "dependOn jar" and changing "from spiJar.archivePath" to "from jar.archivePath" it complained that the task has no history - also unclear.

I'd prefer to find there some simple example that I would be able to apply right away.
In my specific case, I tried to zip the created JAR with all its dependent JARs into a single ZIP.

6.3.4. Creating a distribution

We also add a distribution, that gets shipped to the client:

Example 6.14. Multi-project build - distribution file

api/build.gradle

task dist(type: Zip) {
dependsOn spiJar
from 'src/dist'
into('libs')

{ from spiJar.archivePath from configurations.runtime }

}

 Comments   
Comment by Andrew Schetinin [ 08/Jul/10 ]

Sorry, forgot to put the number of the example to the bug title - please fix.

Comment by Hans Dockter [ 14/Jul/10 ]

I see your point. One reason for this is that at the moment we mix samples and integration tests too much. That makes the samples sometimes to complicated. As we also use snippets from the samples in the user's guide, we get situations like the above.

We are working on getting the samples more simple and extracting the other stuff into distinct integration tests.

Comment by Stevo Slavic [ 14/Jan/14 ]

Bug in example is still there (gradle 1.10 user guide), see 7.3.4. Creating a distribution. Replacing spiJar in there with jar seems to work OK.

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:44:58 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.