Page 1 of 1
Determine installed version of Oxygen XML
Posted: Sat Mar 25, 2023 5:10 pm
by chrullrich
Hello,
is there a way to find out which version of Oxygen XML is installed when using the platform independent distribution (oxygen.tar.gz)? That is, is there a file somewhere that has the release version and/or build number in it?
I have found a few that contain version numbers of components, such as frameworks/dita/DITA-OT3.x/README_OXYGEN.txt:
Code: Select all
DITA Open Toolkit bundled with Oxygen 25.1, build 2023031500
I would prefer a "primary" source, however.
Thanks for any hints.
Re: Determine installed version of Oxygen XML
Posted: Mon Mar 27, 2023 7:50 am
by Radu
Hi,
If you can start Oxygen you can look in the main menu Help->"About" dialog.
Other than that the main version information is located inside a Java class which is part of our main JAR library so it's not something accessible to a script.
Regards,
Radu
Re: Determine installed version of Oxygen XML
Posted: Tue Mar 28, 2023 1:35 pm
by chrispitude
Hi chrullrich,
We have a bash script that dowloads and extracts the platform-independent Oxygen Publishing Engine, then renames the directory according to the Oxygen build number. We use the DITA-OT.README_OXYGEN.txt file for this purpose:
Code: Select all
# rename by build number, then make a filesystem link
BUILD=$(perl -ne 'm{Oxygen \d\d\.\d, build (\d+)} && print $1;' ${OXYPUB}/DITA-OT.README_OXYGEN.txt)
VERSION=$(perl -ne 'm{Oxygen (\d\d\.\d), build \d+} && print $1;' ${OXYPUB}/DITA-OT.README_OXYGEN.txt)
OXYPUB_FULL=${OXYPUB}-${VERSION}-${BUILD}
rm -rf ${OXYPUB_FULL}
mv ${OXYPUB} ${OXYPUB_FULL}
ln -s ${OXYPUB_FULL} ${OXYPUB}
We reference the publishing engine with a filesystem link:
Code: Select all
$ ls -l oxy*
lrwxrwxrwx 1 chrispy chrispy 65 Mar 16 09:55 oxygen-publishing-engine -> /home/chrispy/syncrosoft/oxygen-publishing-engine-25.1-2023031411
drwxr-xr-x 1 chrispy chrispy 512 Mar 16 09:55 oxygen-publishing-engine-25.1-2023031411
drwxr-xr-x 1 chrispy chrispy 512 Mar 15 15:32 oxygen-publishing-engine-25.0-2023012609
By pointing the filesystem link at different installation directories, we can configure the environment to use different publishing engine builds.