History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3388
Type: Improvement Improvement
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Robin Shen
Reporter: J. Mash
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Gradle Wrapper - Enhancement Request

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:

1. WrapperDisabled.jpg
(55 kb)

2. WrapperEnabled.jpg
(66 kb)

 Description  « Hide
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.

 All   Comments   Work Log   Change History      Sort Order:
Change by J. Mash [02/May/19 05:15 PM]
Field Original Value New Value
Attachment WrapperDisabled.jpg [ 10772 ]
Attachment WrapperEnabled.jpg [ 10773 ]

Change by Robin Shen [11/Mar/20 07:34 AM]
Status Open [ 1 ] Closed [ 6 ]
Resolution Won't Fix [ 2 ]