Petals CDK

The pom parent of the component need to be petals-components-sls-parent (version > 3)

To read the version from the manifest, you can use the following source code with a class name defined in the JBI descriptor of the component

String pathToThisClass = Main.class.getResource("/foo/bar/MyClass.class").toString();
String manifestPath = pathToGlazedLists.substring(0, pathToGlazedLists.lastIndexOf("!") + 1) + "/META-INF/MANIFEST.MF";
Manifest manifest = new Manifest(new URL(manifestPath).openStream());

Attributes attr = manifest.getMainAttributes();

String CREATED_BY = attr.getValue("Created-by");
String SOFTWARE_VERSION = attr.getValue(Attributes.Name.IMPLEMENTATION_VERSION);
String SOFTWARE_VENDOR = attr.getValue(Attributes.Name.IMPLEMENTATION_VENDOR);
String SOFTWARE_VENDOR_TITLE = attr.getValue(Attributes.Name.IMPLEMENTATION_TITLE);

Note: don't forget to close stream.

On the component side, just add the maven-jar-plugin to customize the Manifest

Agree with that. With this solution we will be able to differentiate specific customer versions for example.

I prefer:

• First, use the version in the manifest of the jar built by Maven
• If no version available, use the identification extension that is not mandatory.
• If no version available, use a defautlt value 'No version set'

So, only an upgrade version of the CDK is needed to integrate this improvment in our components.
The version can be changed by users using the identification extension. To add it just use the goal 'jbi:configure' of the maven-petals-plugin (an issue should be created for this evolution of the maven-petals-plugin)

I was speaking about that with mathieu.
And we come to that:
-For the current version of the CDK 5.x, we think that using the version in the manifest of the jar built by the JAR maven plugin is the easiest way at runtime to get the version.
-For a futur CDK (6), maybe using the extension of the identification, depends on how we will decide that we handle the conf on that version.

-> The Version will be handled (print, expose to the admin channel) only by the CDK.
is it interesting to get the version at the component specific level? i'm not sure.

Of course, we need to ass a method in the API, for now we try to select the best solution to retrieve the information.

Or we could just add an abstract method in the AbstractComponent class:

String getComponentVersion();

The CDK would use it to get the component version and display this information.

We can use the node identification in the jbi descriptor. This node could be extended.
The result could be :

<component type="binding-component">
<identification>
<name>petals-bc-ftp</name>
<description>fhdhdfh</description>
<cdk:VersionInfo component-version="1.0"/>
</identification>

Why not? Why not using standard thing such as a Version class? This is generally the standard way to provide a version (or the most used in the java world)

And why ?

Some will say that we can not rely on maven for such thing...