Community
Participate
Working Groups
Build ID: I20090430-2300 Steps To Reproduce: Coexist install with Eclipse 3.4.X and 3.5 More information: The cause of the problem is due to the expend flag being changed in the feature. The exact version of such plugin has already been shipped in previous version of WTP, there one should not change the expand flag for it. If you insist of changing the expand flag, you should re-tag the plugin with a new date.
What do you mean by "expand flag"? In the community the version format is known as "major.minor.service.qualifier". Which of them refer to the "expand flag"?
Expand flag is controlled in the feature.
I get it now. Indeed, the "unpack" flag has been changed for this plugin with bug 253855. This is in the org.eclipse.jst.enterprise_ui.feature, revisions 1.42 --> 1.43 of the feature.xml file.
Created attachment 135818 [details] patch
Conan, I must write a description of the problem in order to be approved for 3.1 RC1. I am still not completely sure if I get correctly your problem. How did you face the problem exactly? I assume you had a 3.4.x installation and then you have upgraded to the 3.5 stream and this somehow caused to have the ejb.ui.infopop plug-in doubled. Do I get it correctly?
Yes, I spotted this error in an update scenario. Although I am not directly using the Eclipse Updater.
I know Conan's use-case and while I don't think end-users would hit it, since we don't really support upgrading from a 3.4 install to a 3.5 install (users must start with a fresh Platform) the use-case is valid in the sense of being able to maintain a large repository of plugins that are uniquely identified when they change in any way.
Committed to HEAD and released to 3.1 build.