![]() ![]() ![]() Now data-service team will release SNAPSHOT of its updated code every time to repository, say data-service: 1.0-SNAPSHOT, replacing an older SNAPSHOT jar. Unlike regular versions, Maven checks for a new SNAPSHOT version in a remote repository for every build. SNAPSHOT is a special version that indicates a current development copy. To handle such kind of situation, SNAPSHOT concept comes into play. Now if data-service team uploads a new version every other day, then following problems will arise −ĭata-service team should tell app-ui team every time when they have released an updated code.Īpp-ui team required to update their pom.xml regularly to get the updated version. ![]() Now it may happen that team working on data-service is undergoing bug fixing or enhancements at rapid pace and they are releasing the library to remote repository almost every other day. For example, consider a team is working on the front end of the application as app-ui project (app-ui.jar:1.0) and they are using data-service project (data-service.jar:1.0). A large software application generally consists of multiple modules and it is common scenario where multiple teams are working on different modules of same application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |