[GRADLE-464] make gradles documentation-tasks reusable via plugin Created: 05/May/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Helmut Denk Assignee: Unassigned
Resolution: Won't Fix Votes: 3


the new docbook-based documentation looks very nice
and handy ...

i think it would be very attractive for many
projects to have this way of doing documentations
at hand.

IMO offering docbook/usersguide-tasks via a gradle-docs-plugin
could be a winner ...

Comment by Steve Ebersole [ 03/Dec/09 ]

I discussed this with Adam a bit, specifically in regards to me possibly porting my maven jdocbook plugin to run in gradle as well. Adam had some good ideas about writing a generic framework within gradle to make writing documentation-related plugins easier (having it handle translation iteration, output format iteration, etc). This was all on IRC, though, and the discussion is no longer in my IRC client logs so I do not know exactly what he had in mind in total. I offered to help though in anyway by porting over pieces of the jdocbook functionality.

Comment by Ryan J [ 22/Dec/12 ]

I am also a fan of the Gradle docs and would like this. I tried Steve's gradle-jdocbook plugin (v1.2.1) and it's very close to being a drop in solution that would be good enough for me. Getting it working was relatively painless (one patch to use JDK 7), but the customization is a bit daunting for someone like me who isn't familiar with how all of the transforms and stylesheets work together.

I'd really like to use the gradle-jdocbook plugin, but with a very simple, un-branded theme that would let me ignore everything except the docbook files I'd be writing. The docbook tool-chain is complicated enough that I'd like to close my eyes and pretend it doesn't exist. I'm grateful people are willing to contribute things like Steve's plugin to make life easier for the rest of us and think it would be awesome if it eventually made it's way into the official Gradle distribution.

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