This is now checked in on Develop.
Happy Building!
--Mark
On Tue, May 2, 2017 at 11:46 AM, Udo Kohlmeyer
wrote:
> +1, so have I
>
>
>
> On 5/2/17 11:09, Jared Stewart wrote:
>
>> +1 I've been running with Gradle 3+ without issues too
>>
>> On May 2, 2017, at 11:04 AM, Anthony Baker wrote:
>>>
+1, so have I
On 5/2/17 11:09, Jared Stewart wrote:
+1 I've been running with Gradle 3+ without issues too
On May 2, 2017, at 11:04 AM, Anthony Baker wrote:
+1 I’ve been running against gradle 3+ for awhile now.
Anthony
On May 2, 2017, at 10:55 AM, Mark Bretl wrote:
I have done testing
+1 I've been running with Gradle 3+ without issues too
> On May 2, 2017, at 11:04 AM, Anthony Baker wrote:
>
> +1 I’ve been running against gradle 3+ for awhile now.
>
> Anthony
>
>> On May 2, 2017, at 10:55 AM, Mark Bretl wrote:
>>
>> I have done testing to upgrade our current Gradle wrappe
+1 I’ve been running against gradle 3+ for awhile now.
Anthony
> On May 2, 2017, at 10:55 AM, Mark Bretl wrote:
>
> I have done testing to upgrade our current Gradle wrapper version from
> 2.14.1 to 3.4.1. There are a couple of warnings during the build, however,
> I didn't see anything in a pr
I have done testing to upgrade our current Gradle wrapper version from
2.14.1 to 3.4.1. There are a couple of warnings during the build, however,
I didn't see anything in a precheckin run that would be an issue.
Anybody have any issues with updating Gradle before releasing 1.2.0?
If there no obje
