• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Knute Snortum
  • Paul Clapham
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Frits Walraven
Bartenders:
  • Ganesh Patekar
  • Tim Holloway
  • salvin francis

Gradle version updates  RSS feed

 
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am curious about one thing regarding Gradle usage.

What I noticed is that when I work on an archived app I am automatically promped to upgrade the Gradle version. Despite the fact the source code does not change since 2015.
I also see that upgrading Gradle encourages new features which I do not exactly need; what I would like to get, apparently is an out-dated environment for the app to see it "work as intended" couple updates ago.

I know it may be no longer supported, but my question is; is it possible to create such conditions or I will always be obliged to upgrade ?

Regards.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!