OSGI versioning | Community
Skip to main content
S
Satya_adobe
Level 2
October 16, 2015
Solved

OSGI versioning

  • October 16, 2015
  • 2 replies
  • 1439 views

Hello All,

I have a little confusion regarding the OSGI visioning of the Code packages(CQ - 5.6.1).

In our project, we are following 4 digit visioning, right now the version is 1.4.1.9R, for the next build the version changed to 1.4.1.10R

but osgi is unable to update this version(1.4.1.10R) for the respective bundles and showing as <xyz package - 1.4.1.9R>.

My question here is, should the version of the package be extended to  1.4.1.10 or 1.4.2.1 as per osgi visioning guidelines.

 

Regards

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 Peter_Puzanovs

Hello Satya,

 

Bundle-version follows this format: major.minor.micro.qualifier

You should really have xyz package - 1.4.1.R9 (R letter before number 9)

Which version of apache felix are you using ?

At which stage do you see that OSGi is unable to update your bundle ?

1) Does your jar file contains manifest file with correct Bundle version ?

2) Do you see any previously installed bundles under /install folder ?

3) Can you try to manually remove bundle and install the new bundle ?

Thanks,

Peter

2 replies

Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity AdvisorAccepted solution
Community Advisor
October 16, 2015

Hello Satya,

 

Bundle-version follows this format: major.minor.micro.qualifier

You should really have xyz package - 1.4.1.R9 (R letter before number 9)

Which version of apache felix are you using ?

At which stage do you see that OSGi is unable to update your bundle ?

1) Does your jar file contains manifest file with correct Bundle version ?

2) Do you see any previously installed bundles under /install folder ?

3) Can you try to manually remove bundle and install the new bundle ?

Thanks,

Peter

S
Satya_adobeAuthor
Level 2
October 16, 2015

Thanks Peter,

Below is the version 

Apache License -  Version 2.0, January 2004

As I mentioned the earlier version was  1.4.1.9R

Now we tried upgrading to 1.4.1.10R, which did not work, so we tried moving to 1.4.2.0R and it worked out.

Below are the answers to your questions

1) Does your jar file contains manifest file with correct Bundle version ?

ans:- The manifest file contained 1.4.1.10R, but its not reflecting in OSGI console, the bundle versions are still older(1.4.1.9R)

2) Do you see any previously installed bundles under /install folder ?

and :- No, the new version of jars are getting updated under install folder.

3) Can you try to manually remove bundle and install the new bundle ?

and :- we tried manually remove the bundle and updates the new bundle with version 1.4.1.10R and it worked out
 but we lose all the configuration bindings and we had to bind all the configurations manually.

So what we did is , we installed the older version again 1.4.1.9R, did all the configuration bindings  manually and then  tried a new version as 1.4.2.0R and it worked out.

Terms & ConditionsAccessibility statement

Loading footer...