Community
Participate
Working Groups
The message for deprecatedSyntaxNoPlugin should ideally give some form of identification about the offending plugin or extension; without that info, it is doubtful anyone will ever fix their deprecated code. Message: !ENTRY org.eclipse.wst.common.project.facet.core 2 0 2010-04-26 14:05:45.703 !MESSAGE The ">", ">=", "<", and "<=" notation in version expressions has been deprecated. Note that the angle brackets are represented via "<" and ">" in the plugin.xml files. The functionality has been replaced with range notation. For instance "[X-Y)" means all versions greater or equals to X and less than Y. Open ranges such as "(X" or "Y]" are also allowed.
Created attachment 173338 [details] Patch There was already code in place to report plugin id if the code path in question happened to have this information. The attached patch also adds reporting of the version expr string that was used as well as the facet that it was used with. That should help identify the use site.
Raising for PMC approval for 3.2.1 as this change affects localization. Note that affect is very minor as the affected strings are used in a logged message meant for framework consumers rather than end users.
FYI, for PMC approval, it helps process to put "PMC" in whiteboard ... then it will show up in our PMC review summary pages, such as http://www.eclipse.org/webtools/plans/3.2.1/pmc-bug-approval.php
Released the patch to WTP 3.2.1 and fproj 2.0 streams.