Category
Development projects would need internationalization generally. Most people use property files backed by a ResourceBundle to support it. Developers tend to keep different property files for different countries and keep adding new keys and values whenever they need. If you are a developer, you might have already been there in a situation where once in a while you would need to clean up the property files and remove duplicates.
We often concentrate on the logic and syntax in the beginning of our software career. Eventually there is a time where everyone starts focusing writing a clean and readable code. Writing clean code is hard-work. It takes a lot of effort from a developers side to create a software which is based on simple code.
One of the major benefit Gradle can provide you is continuous build feature. First of all let me explain what is meant by continuous build. A normal build is where you make any changes in the source files (It can be in .java file or in the resources you use) and you need to explicitly build your project to create a new jar/war/ear file.
This post is inspired from the mess I have made in my java project around compile time and runtime dependencies. There are lots of questions you will ask when you try to resolve all the dependencies for your project using tools like Maven or Gradle. These tools make a distinction between compile time and run time dependency, like compile scope, provided scope etc.
We have detected that you are using extensions to block ads. Please support us by disabling these ads blocker.
