[GRADLE-2721] Allow the definition of aliases in build.gradle Created: 25/Mar/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Nathan Wells Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

In order to work with Gradle's alphabetically sorted task dependency list, I created a bit of code that would alias commands to strings of other commands. I did this based on the following threads:

http://gradle.1045684.n5.nabble.com/Aliasing-commonly-repeated-tasks-combination-td4513918.html
http://forums.gradle.org/gradle/topics/how_can_i_enforce_a_chain_of_task_dependency_rules_e_g_clean_first

Here's the code:

def aliases = [
        'build-server': ['clean', 'build', 'fatJar'],
]

def newTasks = []
gradle.startParameter.taskNames.inject(newTasks) { acc, currentTask ->
    acc << aliases[currentTask] ?: currentTask
}
gradle.startParameter.taskNames = newTasks.flatten()

There are surely prettier, groovier, nicer ways of doing this, but I don't have a lot of time to devote to figuring this stuff out. I'd like this functionality to be included in Gradle itself, maybe with an API that looks something like:

aliases

{ 'server-build'('clean', 'build', 'fatJar') }

I know there's a lot of strident discussion about this right now, and I would participate, but found it a PITA to try to subscribe to mailing lists, etc. So, please accept this as a pitiful attempt to contribute.

Thanks

 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 12:29:41 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.