Community
Participate
Working Groups
While fixing bug 349783, I have noticed that the o.e.libra.warproducts.core plugin does not compile against Helios target platform. The o.e.libra.warproducts.core.WARProduct class imports an internal PDE class o.e.pde.internal.core.iproduct.IConfigurationProperty interface that is not available in version 3.6.0 of the o.e.pde.core plugin, but has been introduced in version 3.7.0. However, in the warproduct's bundle manifest the minimum version for the o.e.pde.core dependency is pointed to 3.6.0. This means that the WAR Products feature can install successfully on Helios, but may fail later with runtime errors. I see two possible solutions for this issue: 1) rework the code to remove the dependency to this internal PDE interface. 2) set the o.e.pde.core dependency with correct minimum version - 3.7.0.
It would be best if this can be fixed soon, so it can go in Indigo SR1.
Thanks for reporting. This is fixed in our master.
"fixed in master" means that it's fixed for Juno and will be available with M2. Do you want to fixes this for the Indigo stream too? If, yes then you need to push the change to the indigo branch. Let me know if you want to do this. There is no problem to declare one more M-build for Indigo SR1 with this fix.
Hey Kaloyan. I think it would be good to have it in Indigo SR1. I jus tneed to figure out how to commit in this branch. I tried it but with no success. Will keep you posted.
You should be able to easily cherry-pick your change from 'master' to 'indigo'. Check this guide: http://wiki.eclipse.org/EGit/User_Guide#Cherry_Picking
Thanks for this tip. Every day you learn a new thing about git ;) Done, can you verify it?
Looks like the cherry picking worked well. I also verified that the latest Hudson build does not install successfully on Helios - shows a p2 dependency not satisfied error (which is OK). However, since you did a change in these plug-ins, you now must increment their version from '0.1.0.qualifier' to a higher one - like '0.1.1.qualifier'. Could you do this? In both branches.
Done, thanks for pointing this out ;)
One more thing left :) Now the build fails because of: Unqualified OSGi version 0.1.1.qualifier must match unqualified Maven version 0.1.0-SNAPSHOT for SNAPSHOT builds See https://hudson.eclipse.org/hudson/job/libra-indigo/55/console and https://hudson.eclipse.org/hudson/job/libra/106/console You need to change the version also in the pom.xml so it matches the one in the manifest. Otherwise, Tycho will keep complaining like this.
Done ;)
Build is still failing. It seems like you changed the wrong version number. As far as I can see you change the version of the bundle's reference to the parent project. And the build fails because there is no parent pom with version 0.1.1-SNAPSHOT If the bundle does not specify a version in its pom.xml then it inherits the one from the parent pom, which is 0.1.0-SNAPHOST. In this case you must add a version tag for the bundle explicitly.
Holger, I went ahead and fixed those poms. You can check the change here: http://git.eclipse.org/c/libra/org.eclipse.libra.git/commit/?h=indigo&id=5075889ffe61eea7afe2c5770b93c33232300f0b I will release the M-build later today.
I had to increment also the version of the WAR Product feature and adjust the category.xml so the new version appear correctly in the p2 repository.
