OLAP4J是否已停止维护？有无合适的等效替代方案？

Great question—let's break this down clearly based on the evidence you've shared and some practical alternatives for Java XMLA integration.

Is OLAP4J effectively unmaintained? #

Yes, all available signs indicate OLAP4J has been effectively abandoned since around 2016:

• The official website hasn't been updated since 2013
• The project's development mailing list went silent with its last message in May 2016
• The last stable, widely usable release is version 1.2.0, published back in 2016
• While there are newer release tags in the project's source repo, none of these builds have been pushed to public Maven repositories—so they're not accessible for standard Java project setups

Recommended Alternatives #

If you need a maintained Java solution to connect to XMLA services, here are solid options to consider:

• XMLA4J: A lightweight, purpose-built library focused solely on XMLA interactions. It's actively maintained, supports modern XMLA features, and is available in Maven Central. Use it to run MDX queries, browse cube metadata, and handle OLAP operations without the broader (now unmaintained) scope of OLAP4J.
• Apache Calcite: Though primarily a SQL query engine, Calcite includes robust support for integrating with OLAP systems via XMLA. As an Apache Software Foundation project, it's actively maintained with a strong community. You can use Calcite to translate SQL to MDX or interact directly with XMLA endpoints.
• Custom Lightweight Client: For simple use cases (like executing basic MDX queries), you can roll your own minimal client using standard Java tools: HttpClient for SOAP requests, and XML parsers like Jackson XML or JAXB to handle response parsing. This gives you full control but requires direct handling of XMLA's SOAP protocol.

内容的提问来源于stack exchange，提问作者jon hanson