# Liquibase Java API vs CLI vs MVN

**URL:** <https://forum.liquibase.org/t/liquibase-java-api-vs-cli-vs-mvn/7126>\
**Category:** General Discussion\
**Created:** [July 30, 2022, 1:26pm UTC](https://forum.liquibase.org/t/liquibase-java-api-vs-cli-vs-mvn/7126 "2022-07-30T13:26:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shenoy.ganesh.kumar](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@shenoy.ganesh.kumar](https://forum.liquibase.org/u/shenoy.ganesh.kumar)\
**Post date:** [July 30, 2022, 1:26pm UTC](https://forum.liquibase.org/t/liquibase-java-api-vs-cli-vs-mvn/7126/1 "2022-07-30T13:26:46Z")

</div>

We understand that now pro vs opensource are delivered as 2 different packages. Also we have found three ways to integrate liquibase -

1. CLI
2. MVN
3. Java API

We are inclined to use Java API for our specific use case. But we would like to know, any of the above we select, all three are having same features and if any chance of differences in features later. Please can we get some pointers around this query. Thanks in advance.

---

<div class="post-metadata">

**Author:** ![ktaggart](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ktaggart/32/596_2.png) [@ktaggart](https://forum.liquibase.org/u/ktaggart)\
**Post date:** [August 8, 2022, 5:56pm UTC](https://forum.liquibase.org/t/liquibase-java-api-vs-cli-vs-mvn/7126/2 "2022-08-08T17:56:52Z")

</div>

There are no plans to make open source features available in one method and not the other. There should be parity. Occasionally, when a command parameter is added, one method might be missed, but it’s not a big lift for that to be resolved. There are obviously feature differences between Pro and Open Source.

I am curious, what is your specific use case and why are you leaning towards the Java API?