I have checked in the update to move the Gradle Wrapper to 3.5.1, with the
fix for Eclipse IDE, into the develop branch.
Hopefully this time we won't need to revert it.
--Mark
On Tue, Jul 25, 2017 at 2:50 PM, Mark Bretl wrote:
> Now that we have 1.2.0 out the door, would I be able to get someo
Now that we have 1.2.0 out the door, would I be able to get someone to
verify my fixes from those who were having trouble with Gradle 3.4.1 in
their IDE?
Thanks,
--Mark
On Wed, Jun 14, 2017 at 5:08 PM, Mark Bretl wrote:
> I think I figured it out.
>
> Here is what I did:
> Fix was to declare t
I think I figured it out.
Here is what I did:
Fix was to declare the version of Antlr in the dependencies{} because if no
version is set, the ANTLR plugin would default to 2.7.7. This was causing
issues since the ANTLR plugin was trying to 'change' the version after
dependency resolution for its c
I think we have to check the ANTLR plugin to understand it's requirements..
maybe there is a newer plugin version for ANTLR
On 5/9/17 10:00, Kirk Lund wrote:
I've reverted the upgrade to gradle 3.4.1. I also went ahead and created a
branch that repeats the upgrade:
feature/gradle-3.4.1
Feel f
I've reverted the upgrade to gradle 3.4.1. I also went ahead and created a
branch that repeats the upgrade:
feature/gradle-3.4.1
Feel free to experiment with that branch.
On Tue, May 9, 2017 at 9:53 AM, Kirk Lund wrote:
> I'll go ahead and revert the upgrade. Hopefully we can eventually find t
I'll go ahead and revert the upgrade. Hopefully we can eventually find the
cause so we can repeat the upgrade.
On Mon, May 8, 2017 at 4:19 PM, Bruce Schuchardt
wrote:
> The "eclipse" target fails, too.
>
> Le 5/8/2017 à 3:32 PM, Kirk Lund a écrit :
>
>> I want to revert the gradle upgrade becaus
The "eclipse" target fails, too.
Le 5/8/2017 à 3:32 PM, Kirk Lund a écrit :
I want to revert the gradle upgrade because it breaks IntelliJ and the idea
gradle task. Please let me know if you have a problem with this.
PS: Please be prepared to help me if you vote against me reverting the
upgrade
+1 With multiple contributors unable to build, I think we ought to revert the
upgrade.
> On May 8, 2017, at 4:00 PM, Bruce Schuchardt wrote:
>
> +1 let's revert it
>
> Le 5/8/2017 à 3:32 PM, Kirk Lund a écrit :
>> I want to revert the gradle upgrade because it breaks IntelliJ and the idea
>> g
+1 let's revert it
Le 5/8/2017 à 3:32 PM, Kirk Lund a écrit :
I want to revert the gradle upgrade because it breaks IntelliJ and the idea
gradle task. Please let me know if you have a problem with this.
PS: Please be prepared to help me if you vote against me reverting the
upgrade ;) I really w
I upgraded gradle on my Ubuntu box and am hitting this problem there.
Not a problem on Windows for some reason.
Le 5/8/2017 à 3:50 PM, Patrick S Rhomberg a écrit :
I upgraded my gradle to match yours and am still experiencing the issue.
I appear to be using Java 1.8.0_121 and am on Mac.
grad
I upgraded my gradle to match yours and am still experiencing the issue.
I appear to be using Java 1.8.0_121 and am on Mac.
gradle --version
Gradle 3.5
Build time: 2017-04
I'm using gradle 3.5 and am not having this problem.
> gradle --version
Gradle 3.5
Build time: 2017-04-10 13:37:25 UTC
Revision: b762622a185d59ce0cfc9cbc6ab5dd22469e18
+1 for revert... My build broke as well... after reverting, everything
just worked :)
On 5/8/17 15:32, Kirk Lund wrote:
I want to revert the gradle upgrade because it breaks IntelliJ and the idea
gradle task. Please let me know if you have a problem with this.
PS: Please be prepared to help m
13 matches
Mail list logo
