Likelihood to Recommend Maven is great if you have an application with a lot of third-party dependencies and don’t want each developer to keep track of where the dependency can be downloaded. It’s also a great way to make it easy for a new developer to be able to build the application. It’s less suitable for simple projects without any third-party dependencies.
Read full review Liquibase is very well suited for database schema management. It works great for any DDL/DML deployments, changes made to database are easy to manage, track or troubleshoot. It comes with a wide variety of Rollback options. Liquibase Policy checks are a great way to enforce standards around Database code development across organization and prevent any unexpected from being deployed
Read full review Pros If you are building in the Java ecosystem, then Maven definitely has the biggest repository of artifacts needed for such projects. It has a very simple to use extendable architecture. Everything is configurable through the Pom.xml file which is very simple to follow. Read full review Automation - Improved data integrity and security validation, Expanded support for non-relational database types Observability - Reports for code quality, security checks, updates, rollbacks, and Flows Governance- Increased control of privileges and access for groups and individual users Tracks every database changes by enforcing policy and compliance Efficient - Standardized and self-service driven deployment process Tracks every database changes by enforcing policy and compliance Efficient - Standardized and self-service driven deployment process Read full review Cons Maven provides a very rigid model that makes customization tedious and sometimes impossible. While this can make it easier to understand any given Maven build, as long as you don’t have any special requirements, it also makes it unsuitable for many automation problems. Maven has few, built-in dependency scopes, which forces awkward module architectures in common scenarios like using test fixtures or code generation. There is no separation between unit and integration tests Read full review Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9 We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase Liquibase should rollback the if any one of the changes fails. Read full review Likelihood to Renew We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.
Read full review Usability The overall usability of Apache Maven is very good to us. We were able to incorporate it into our company's build process pretty quickly. We deployed it to multiple teams throughout the entire enterprise. We got good feedback from our developers stating that Apache Maven has simplified their build process. It also allowed to to standardize the build process for the entire enterprise, thus ensure that each development team is using the same, consistent process to build code.
Read full review Build process is too time consuming and getting extra DB instance takes a toll
Read full review Support Rating I can't speak to the support, as I've never had issues. Apache Maven "just works," and errors were user errors or local nexus errors. Apache Maven is a great build/dependency management tool. I give it a 9/10 because occasionally the error message don't immediately indicate a solution...but again, those errors were always user or configuration errors, and the Maven documentation is extensive, so I don't find fault in Maven, but in its users.
Read full review I gave this rating because I feel their customer support staff have a very good and deep knowledge about the product and they are very helpful when we are stuck on something. The customer support is passionate about their product and they are always ready to help their customer as quickly as possible.
Read full review Implementation Rating the database deployments helped us with increased productivity, faster delivery and low risk.
Read full review Alternatives Considered Ant, Maven's opposing framework, is often a point of comparison. Although Ant does not require formal conventions, it is procedural in the sense that you must tell Ant exactly what to do and when. It also lacks a lifecycle, along with goal definition and dependencies. Maven, on the other hand, requires less work as it knows exactly where your source code is as long as the pom.xml file is generated.
Read full review There is no real competitor when it comes to what Liquibase does - at least not at the time we considered it three years ago. It was an easy choice in this regard, but we could have said no to it if it made our workload more difficult. But our proof of concept showed there were easy wins to be had by implementing its software.
Read full review Return on Investment Apache Maven is an open source product from the Apache Software Foundation. Being free to use without any licensing constraints, we've been very happy with this product thus far. The software build and packaging times for our applications have improved greatly since our use of this tool. Read full review We need to re-educate developers to use Liquibase. In some cases, it is hard to align when several teams work on the same DB. On the other hand, Liquibase provides order and consistency in managing DB changes. Evidence and traceability are a plus. Read full review ScreenShots