Apache Maven vs. OpenText Web CMS

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.

Incentivized

OpenText TeamSite is well-suited to large, enterprise-wide implementations where customization, content governance, and dynamic content distribution is needed or prioritized. It is probably not ideal for smaller sites with simple architecture and few resources to manage custom implementation.

Incentivized

• 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.

Incentivized

• The drag and drop forms feature makes publishing simple and quick.
• Preview of customer data before sending publications helps us to deliver personalized experiences.

Incentivized

• 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

Incentivized

• I have recommendation for improvements.
• It is easy to work with all the features.
• All necessary content management tools are included.

Incentivized

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.

Incentivized

Overall, it's a solid package with the potential to offer much functionality with appropriate resources applied. There are a few issues with the authoring interface that OpenText should address before its a top shelf authoring experience.

Incentivized

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.

Incentivized

Our technical resources engage with OpenText TeamSite so I don't have direct experience. However, critical issues that we need help with seem to get the attention they deserve without issue. However, training and user resources for business owner roles are a bit lacking and some annoying issues with the authoring interface should be addressed sooner.

Incentivized

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.

Incentivized

It offers more content editing features at a relatively low cost thus overall deployment is lower in cost. It has great customer support who are always there to support and answer to our needs thus making the process of deployment seamless at every stage and offering training for working with their product.

Incentivized

The annual contract should be clearer in terms of the breakdown of user license types (system admin, admin, regular user, etc).

Incentivized

• It was very handy to roll out organization level frameworks to be used by diverse departments and business
• Consistent build artifacts enabling smooth release cycles, thereby enabling to adhere to release calendars and feature rollouts
• Reduced 80 man hours of work every release cycle

Incentivized

• We integrated with google analytics, now we have the proper comprehension of our audience data reception and behaviors - we've greatly improved on personalized marketing.
• Quick publication of content across the main digital channels.
• We run our digital campaigns swiftly.
• We've maintained our brand consistency for three years.

Incentivized