Quarkus中groupId io.quarkus与io.quarkus.platform的区别是什么？

Great question! Let's break down the key differences between these two group IDs in the Quarkus ecosystem:

Core Purpose & Functionality #

• io.quarkus: This was the original group ID used for Quarkus dependencies prior to version 2.0.0. It refers to individual Quarkus component artifacts (like quarkus-resteasy or quarkus-hibernate-orm), but doesn't enforce automatic version alignment across all your project's dependencies. You'd have to manually sync versions for each extension to avoid conflicts.
• io.quarkus.platform: Introduced as the recommended approach in newer versions, this group ID provides Quarkus Platform BOMs (Bill of Materials). These BOMs are curated sets of pre-tested, compatible versions for every Quarkus extension and its underlying dependencies. Using this group ID ensures all your dependencies work seamlessly together without manual version juggling.

Version Management Experience #

• With io.quarkus, updating one extension might require checking and updating multiple other related dependencies to maintain compatibility—easy to miss and prone to errors.
• With io.quarkus.platform, you only need to specify a single platform version in your build file. All extensions and their dependencies will automatically pull in versions that are verified to work with that platform release, drastically simplifying dependency management.

Adoption Timeline #

• Before Quarkus 2.0.0, all starter projects and documentation defaulted to using io.quarkus directly.
• Post-2.0.0, official Quarkus starter projects and guides now use io.quarkus.platform as the standard, since it eliminates compatibility headaches and streamlines project setup.

In short: io.quarkus.platform is the modern, hassle-free way to manage Quarkus dependencies, while io.quarkus is the older approach that requires more manual oversight.

内容的提问来源于stack exchange，提问作者Jaqueline Schweigert