Project version (pom.xml), package version and bundle version | Community
Skip to main content
daniel_henriqu1
New Participant
April 27, 2017
Solved

Project version (pom.xml), package version and bundle version

  • April 27, 2017
  • 2 replies
  • 1829 views

Hi, everybody.

In a project structure created using Adobe Maven Archetype or Marketing Cloud Maven Archetype, can I use "anything" as the project version of my POMs?
Or some values may lead to inconsistencies in the Package Manager and/or in the OSGI installer?

I mean, are all the following valid values?

  • 1.0
  • 1.0.0
  • 1.0.0.0
  • 1.0.0.0.0
  • 1.0.0alpha
  • 1.0.0-alpha
  • 1.0-SNAPSHOT
  • 1.0.0-SNAPSHOT
  • 1.0.0.0-SNAPSHOT
  • 1.0-beta-SNAPSHOT
  • 1.0_beta-SNAPSHOT
  • 1.0.0.0-alpha1-rc3-SNAPSHOT
  • 1.0.0.0_alpha1_rc3-SNAPSHOT

Will they all work as project version, package version (META-INF/vault/properties.xml) and bundle version (META-INF/MANIFEST.MF) as well?
Despite the special use of the "-SNAPSHOT" suffix, am I allowed to use any sequence of [a-zA-Z0-9.-_] as version, without negatively affecting the installation process?

Thanks in advance!

Best regards,

Daniel.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Feike_Visser1

See attached a screenshot from /system/console/bundles, as you can there is a variety of version-formats.

2 replies

daniel_henriqu1
New Participant
April 27, 2017

Great idea, Feike!

Applying the same principle to JCR packages (using Query Builder Tool and Query Builder Debugger), I've been able to check the whole variety of version numbers used in my current AEM installation.

Some examples:

  • 0.0.10
  • 0.0.12-CQ620-B0002
  • 0.0.22
  • 0.0.78-CQ620-B0001
  • 0.0.8
  • (...)

Thank you!

Feike_Visser1
Feike_Visser1Accepted solution
Employee
April 27, 2017

See attached a screenshot from /system/console/bundles, as you can there is a variety of version-formats.