Thanks for looking into this, Tim. This approach makes sense. I will open the two bugs and release the immediate M3 fix shortly. - Konstantin
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim deBoer Sent: Monday, November 12, 2007 8:52 AM To: [email protected] Subject: Re: [wtp-dev] Problem related to org.eclipse.runtime.compatibilityin M3 candidate build Hi Konstantin, I took a look, and the problem is that the wst.common.ui plugin has the following <require>: <import plugin="org.eclipse.core.runtime.compatibility" version="3.1.100" match="equivalent" /> Since the o.e.core.runtime.compatibility plugin has changed it's version to 3.2.0, this dependency breaks. The quickest solution is for us to either bump up the version to 3.2.0 or change the match to 'compatible'. As far as I can tell, org.eclipse.wst.common.ui.properties is the only WTP plugin that depends on this plugin, so none of our other features should have this problem. I agree we should remove the dependency entirely, but that could be dangerous since we have to declare M3 by Wednesday. I would suggest opening up one critical bug to get the feature fixed this week, and a second to investigate removing the dependency from plugin and feature in M4. Thanks, Tim From: "Konstantin Komissarchik" <[EMAIL PROTECTED]> To: "General discussion of project-wide or architectural issues." <[email protected]> Date: 11/12/2007 10:54 AM Subject: [wtp-dev] Problem related to org.eclipse.runtime.compatibility in M3 candidate build ________________________________ I doing some testing with the M3 candidate build and wanted to install some BEA plugins via an update site. I got the following message in the install update wizard. Does anyone know what's going on here? WST Common UI (2.1.0.v200709192200-7C6EIbE9RvTVnoosrln7YgYagz-Z) requires plug-in "org.eclipse.core.runtime.compatibility (3.1.100)", or equivalent. Does our distribution need to include some other platforms plugins that are currently not referenced? What would it take to eliminate this dependency, since it looks like the platform team is done supporting it? This seems like a pretty critical issue to sort out prior to declaring M3 as it will be a serios blocker for adopters if no updates can be installed. - Konstantin Konstantin Komissarchik Staff Software Engineer Phone: 206.926.2962 IM: kosta0120 on Yahoo [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> BEA Systems, Inc. 999 North Northlake Way Seattle, WA 98103 www.bea.com <http://www.bea.com/> Barring that natural expression of villainy which we all have, the man looked honest enough. Mark Twain Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it._______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev <https://dev.eclipse.org/mailman/listinfo/wtp-dev> Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
<<ATT30729800.gif>>
<<ATT30729801.gif>>
<<ATT30729802.gif>>
<<ATT30729803.gif>>
<<ATT30729804.gif>>
<<ATT30729805.gif>>
<<ATT30729806.gif>>
<<ATT30729807.gif>>
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
