I'm developing a plugin that the gradle build uses. I (somewhat foolishly) had the build set to pick up the latest version of the plugin. I recently made some changes to the plugin and some changes to gradle-core to support it, but because you are working on a fork of gradle you picked up the new version of the plugin, but not the changes to core.
So yeah, sorry about that :/ On Tue, Jul 15, 2014 at 10:38 AM, KARR, DAVID <dk0...@att.com> wrote: > Ok, that fixed it. Would you mind elaborating on this? What was the > root cause that you resolved? > > > > *From:* Perryn Fowler [mailto:perryn.fow...@gradleware.com] > *Sent:* Monday, July 14, 2014 5:33 PM > *To:* dev@gradle.codehaus.org > *Subject:* Re: [gradle-dev] Getting "Failed to notify profile listener" > in Gradle userguide build > > > > sigh. That was meant to say > > > > "Ok TRY building now using the '--refresh-dependencies' flag" > > > > On Tue, Jul 15, 2014 at 9:20 AM, Perryn Fowler < > perryn.fow...@gradleware.com> wrote: > > Ok building now using the '--refresh-dependencies' flag > > > > On Tue, Jul 15, 2014 at 9:14 AM, Perryn Fowler < > perryn.fow...@gradleware.com> wrote: > > actually give me a few mins and I can probably fix it my end > > > > On Tue, Jul 15, 2014 at 9:05 AM, Perryn Fowler < > perryn.fow...@gradleware.com> wrote: > > Except of course you would be working on a fork, so you would need to do > something like this https://help.github.com/articles/syncing-a-fork > > > > Failing that you can temporarily comment out line 121 (apply from: > "gradle/analytics.gradle") in build gradle > > > > On Tue, Jul 15, 2014 at 8:58 AM, Perryn Fowler < > perryn.fow...@gradleware.com> wrote: > > Sorry that is probably my fault - if you 'git pull --rebase' it should be > fixed? > > > > > > > > >
