org.eclipse.platform.doc.isv/porting/3.2/faq.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.6 - (view) (download) (as text)

1 : jeem 1.1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
2 :     <html>
3 :    
4 :     <head>
5 :    
6 :     <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
7 :    
8 :     <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
9 :     <meta http-equiv="Content-Style-Type" content="text/css">
10 :     <link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
11 :     <title>Eclipse 3.2 Plug-in Migration FAQ</title>
12 :     </head>
13 :    
14 :     <body>
15 :    
16 :     <h1>Eclipse 3.2 Plug-in Migration FAQ</h1>
17 : dpollock 1.2 <ol>
18 :     <li><a href="#legacyActionWithNoLabel">Legacy Action With No Label</a></li>
19 : dj 1.5 <li><a href="#qualifiedIDs">Usage of IDs with dots (&quot;.&quot;) in Extension Points, Extensions, and Content Types</a></li>
20 : dpollock 1.2 </ol>
21 : sdimitro 1.4 <h2><a name="legacyActionWithNoLabel">Legacy Action With No Label</a></h2>
22 : dpollock 1.2 <p>
23 :     If you are using the action-based extension points, then you may want to specify
24 :     either a <code>definitionId</code> or a non-empty <code>label</code>. If you
25 :     don't do this, then in the "Uncategorized" category, there may be commands
26 :     called "Legacy Action With No Label". They will appear in the keys preference
27 :     page. A warning will be printed to the log.
28 :     </p>
29 :     <p>
30 :     In 3.2, all actions are converted into commands when parsing the registry. As
31 :     such, actions without a definition id have a command generated for them. This
32 :     command needs a label, which is typically drawn from the label on the action.
33 :     In the case of actions appearing in the tool bar, sometimes neither a definition
34 :     id nor a label were specified.
35 :     </p>
36 : dj 1.5
37 :     <h2><a name="qualifiedIDs">Usage of IDs with dots (&quot;.&quot;) in Extension Points, Extensions, and Content Types</a></h2>
38 :     <p> In the past, IDs specified for extension points, extensions, and content types were expected
39 :     to be &quot;simple IDs&quot; with no dots in them (e.g., &quot;myPoint&quot;, not &quot;my.Point&quot;,
40 :     not &quot;myPlugin.myPoint&quot;). This rule was specified, but not enforced.</p>
41 :     <p> In the release 3.2 we added processing of fully-qualified IDs (e.g., &quot;org.eclipse.myPlugin.myPoint&quot;).
42 :     However, it turned out that some components had previously used IDs with dots and the change broke
43 :     functionality provided by those components. To preserve backward compatibility for IDs of extension points
44 :     and extensions, we added special processing based on the version of the XML file:</p>
45 : curtispd 1.6 <ul>
46 : dj 1.5 <li>If the XML file has the tag &lt;?eclipse version=&quot;3.0&quot;?&gt;, the runtime
47 :     functionality remains the same as before (plug-in ID is added to the simple name)</li>
48 :     <li>If the XML file has the tag &lt;?eclipse version=&quot;3.2&quot;?&gt;, the IDs with dots are treated as fully qualified
49 :     names (no plug-in ID is added to the name).</li>
50 : curtispd 1.6 </ul>
51 : dj 1.5 <p> Details can be found in the bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=128866">128866</a>.</p>
52 :     <p> We recommend switching to the 3.2 format as the usage of IDs with dots was never intended to be supported in
53 :     the 3.0 format. (Simply put, there is no guarantee that it works in all cases today or that it will work the same
54 :     tomorrow.)</p>
55 :     <p> This processing of the &lt;?eclipse version&gt; tag applies to IDs of extension points and extensions, but not to
56 :     the IDs of content types (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139491">139491</a>).</p>
57 :    
58 : jeem 1.1 </body>
59 :    
60 :     </html>