Re: [beanutils] Gradle build weirdness

Ya I got it resolved, the culprit was spring boot plugin. They created their own dependency management within Gradle. The thread is updated with the cause and workaround. On Wed, Sep 28, 2016 at 3:25 PM, Oliver Heger wrote: > > > Am 27.09.2016 um 18:47 schrieb

Re: [beanutils] Gradle build weirdness

Am 27.09.2016 um 18:47 schrieb Raviteja Lokineni: > Does anyone have any fix for it or have experienced the same? Did you get this resolved? I just replaced the dependency in a Maven build, and the new version was picked up immediately. So I think the deployment to Maven central and meta data

Re: [beanutils] Gradle build weirdness

Does anyone have any fix for it or have experienced the same? On Tue, Sep 27, 2016 at 12:45 PM, Raviteja Lokineni < raviteja.lokin...@gmail.com> wrote: > Hi all, > > I had been using beanutils 1.9.2 as a runtime dependency in a gradle > build. After the release of 1.9.3 version, I've upgraded

[beanutils] Gradle build weirdness

Hi all, I had been using beanutils 1.9.2 as a runtime dependency in a gradle build. After the release of 1.9.3 version, I've upgraded the version in build.gradle but gradle somehow still picks up the older jar, although there is no reference of it. More information on a gradle forums (didn't