![]() ![]() This way, whenever we create a new version and deploy it, we can pass the version number from our CI/CD tool easily without directly editing the pom file. If you know how to write new libraries, no one can stop you from taking advantage. Can you imagine if they didn’t exist and we needed to write them every time we start a new project? Not funny, right. Yes, they maybe right for some scenarios like the one I have explained beforehand, but think of all those ready-to-use libraries we use in many spring boot projects we have. We should be able to update the dependencies of the application or add extra dependencies without triggering a dependency problem due to that sticky library.įor these reasons, some people say that libraries are bad. Don’t forget that our application must not depend on the library project. If you use lots of dependencies for pure joy, they will lead to some annoying problems. One of the biggest problems we can have when writing a library project is the strong relationship with the application for which we will use it. So, they should require as few dependencies as possible. If they are very dependent on other modules, it would be difficult to maintain and integrate them. They must only do what they are supposed to do. When writing a library project, there are some important points to keep in mind.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |