| Key: |
QB-3388
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Won't Fix
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
J. Mash
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 02/May/19 05:12 PM
Updated: 11/Mar/20 07:34 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
|
Currently, the Gradle build step allows the user to specify the path to the wrapper executable file, but this becomes quite cumbersome to support in large-scale (hundreds of repos), cross-platform environments.
Ideally, the Gradle build step would first provide a checkbox to disable/enable the usage of the wrapper, then present the user with a textbox allowing them to specify the DIRECTORY where the wrapper lives (which would default to the current workspace, if empty).
I'll add mockups for clarity in a moment.
|
|
Description
|
Currently, the Gradle build step allows the user to specify the path to the wrapper executable file, but this becomes quite cumbersome to support in large-scale (hundreds of repos), cross-platform environments.
Ideally, the Gradle build step would first provide a checkbox to disable/enable the usage of the wrapper, then present the user with a textbox allowing them to specify the DIRECTORY where the wrapper lives (which would default to the current workspace, if empty).
I'll add mockups for clarity in a moment. |
Show » |
| No work has yet been logged on this issue.
|
|
Gradle Wrapper - Enhancement Request
