[GRADLE-781] Default Tasks Created: 15/Dec/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Ken Sipe Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

There are some common tasks floating around the web... such as:
task initProject(description: 'Initialize project directory structure.') << {
// Default package to be created in each src dir.
def defaultPackage = 'com/xxx/blog'

['java', 'groovy', 'resources'].each {
convention.sourceSets.all."${it}".srcDirs*.each

{ dir -> def newDir = new File(dir, defaultPackage) logger.info "Creating directory $newDir" // gradle -i shows this message. newDir.mkdirs() // Create dir. }

}
}

The gradle wrapper task probably falls into this category. These are tasks that run once and that's usually it. It would be nice if these were default tasks (no configuration in the build file)... with the ability to override in the config file.

 Comments   
Comment by Hans Dockter [ 16/Jan/10 ]

We might bundle those in plugins (Wrapper Plugin, ...).

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