Java storage jar maangement
Brought to you by:
yvesyang
Menu
▾
▴
#53 Java storage jar maangement
In current implementation, the project references to the Java data storage jar in a complete name, that include the build number. When we migrate to a new build, the project cannot find the org.soyatec.windows.azure.jaav.xx.jar. Therefore, the project is useless.
We need a dynamic resolution solution.
Our current solution try to resolve bundle org.soyatec.windows.azure.java, and get its path from eclipse platform. We do not reference to the build version number.
In the first implementation, we copied the jar in the resource folder. It has been changed by me to copy the jar by resolution of the bundle in eclipse. But the project does keep the entire information (including the version and build number) . When eclipse migrates to a new version of org.soyatec.windows.azure.java, the project cannot find the previous jar.