[GRADLE-74] Add upload functionality for reports Created: 29/Apr/08  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Hans Dockter Assignee: Unassigned
Resolution: Won't Fix Votes: 3


We would like to support uploading of reports as part of the Java plugin. We need to support different protocols for this. Let's see if we can use the Ivy resolvers for this.

Comment by Antony Stubbs [ 12/Jul/08 ]

Shouldn't this be abstracted out of simple the Java plugin? Surely other plugins will want to re-use some sort of report uploading functionality?

Comment by Hans Dockter [ 12/Jul/08 ]

It should be. There is at least the abstraction of generating and uploading something to a website. So what might make sense is to have a html_upload folder where any task can contribute to (reportings tasks or whatever else). A website plugin would take care of uploading this folder to the website.

On the other hand I have the following attitude at the moment. There are some painfully missing features:

  • Reporting
  • IDE file generation
  • Better logging
  • TestNG support
  • EAR archive support
  • Jetty Integration for testing webapps

I would like to have them ASAP. For many people one or the other feature of this list is a prerequisite for using Gradle. I'm happy to add them in a simple fashion first (simply to the Java Plugin). After this we would start to implement a rich plugin system. It will be easy to wrap the logic of the features above into the new plugin system.

At least this is how I see things now.

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