[GRADLE-328] Section 10.8.2 of the user manual (p30) should clarify what it means by 'myZipTask' (relate to archive_...) Created: 20/Dec/08  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Jon Cox Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

The way in which calling jar(), zip(), tar(), tarGz, and tarBzip2()
within bundle tasks IMPLICITLY creates tasks named archive_<...>
where the <...> part depends on badly documented parameters
to these functions is a bit tricky to grasp the first time around.

What made this much harder was that section 10.8.2 said:

myZipTask.fileDirSet( .... )

{... }

It would have make things easier to get had the docs
used an example like:

archive_jar.fileDirSet(...)

{ ... }

Then go on to give another example:

archive_zip.fileDirSet( ... ) { ... }

Then reinforce how you can say:

archive_zip

{ .... }

Also, this would be a good place to talk about how you can (or can't ?)
control the name of the task that is created by calling jar(), zip() , etc.
The first few times through these docs I kept asking myself
"wait... how to I get libs/dists to make a custom-named zip/jar task?"
With examples like those provided above, this stumbling block would
have been removed.

 Comments   
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:27:22 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.