| [tycho-user] working with .product-version - versionmanagement |
|
Hi there, we changed our developing way from monolith to microservices in the past one and a half year. For the lot of services we’ve created so far it’s very important for us to create a good
versions structure. Therefore we’re searching a good way for version-management.
One of our goals is to create a way of providing a hint for the version number. In our old days we’ve created a static config.ini and every build copied it to the right place and
replaced the placeholders with our versionnumber. We used this trick to see the versionnumber in the config.ini itself and in the .log-files. #Product Runtime Configuration File eclipse.application=com.application osgi.bundles.defaultStartLevel=4 …. osgi.bundles= org.eclipse.equinox.common@2:start,\ … osgi.classloader.type=parallel eclipse.buildId=${product.version} ${buildNumber} This works fine if there is a static config.ini. But we don’t want to create a static config.ini for every of our products. Because that limits our use of the .product-Editor. So I hoped there is a way that Tycho will do the work for us.
I think there should be a way to read the version number from the .product-File or another way to provide this version (https://bugs.eclipse.org/bugs/show_bug.cgi?id=508293)
to the build. And when the product get materialized all placedholders will replaced with the linked variables. Is this a realizable scenario or is there any other way to provide the versionnumber without adding any special goals and copying files around? One way I tried is to use set-version and use the pom-version as the main version which is valid solution for us. But I didn’t find any way to provide this variable to the config.ini
without using the “old way”. We really want to have a version hint in the deployed products. And by the way :D Thanks for all the good work with Tycho so far!
|
