title: Eclipse plugin developed under Helios doesn't show in Juno
body: <p><strong>I developed a plug-in for Eclipse that has been working fine in Helios.</strong>  I installed Juno, put the plug-in jar in the dropins folder, and started Eclipse, but <strong>the plug in does not work in Juno</strong> (my extra menu item does not show-up).</p>
  
  <p>When I view plug-ins, I see my plug-in in the list.  I figure it must be some kind of version problem (<a href="https://stackoverflow.com/questions/1491143/eclipse-plugin-not-working-in-ganymede-but-working-in-galileo">something like this</a>), but when I created the plug-in, I did not specify a max version, only minimum versions.  I did notice it's not signed like the rest of the plug-ins, but I don't think that should stop it from working.</p>
  
  <p>So I opened up the plug-in development project with Juno and tried to run it via "Launch an Eclipse application" under "Testing".  Same result (no menu item).  I even removed the min version (using the "Properties..." button).  Still no joy.  When I do the above with Helios, it works (menu item shows).</p>
  
  <p>In my "Required Plug-ins", I have org.eclipse.ui, org.eclipse.core.runtime, org.eclipse.jdt.core, org.eclipse.core.resources, org.eclipse.ui.console, org.eclipse.jface.text, <strong>all without any min or max versions</strong>.  And those same entries show when I click "Show the plug-in dependency hierarchy".  Everything seems to be in order, yet my app doesn't seem to run.</p>
  
  <p><code>Plug-in Registry &gt; (right click on my plugin) &gt; Show Advanced</code></p>
  
  <p><code>Plug-in Registry &gt; (right click on my plugin) &gt; Diagnose</code></p>
  
  <p>results in a <strong>No problems detected.</strong></p>
  
  <p><code>Plug-in Registry &gt; (right click on my plugin) &gt; Start</code></p>
  
  <p>results in a green triangle, but there is still no menu item.</p>
  
  <p>I even set up a feature update site; completely under Helios, I created a local feature update site, removed the jar file from the Helios drop-ins directory, and installed the app from the site.  Worked perfectly.  But when I installed from Juno the same way, it showed in the plug-in registry, but again, no menu entry. It seems to be getting found, just not apparently running (as indicated by the lack of a menu item in the expected place).</p>
  
  <p>Under <code>Extensions &gt; org.ecliipse.ui.menus &gt; menuContribution</code> I see my menu item there, with <code>locationURI=popup:org.eclipse.jdt.ui.PackageExplorer</code>.  Did something change between Helios and Juno with this maybe?</p>
  
  <p><strong>Update:</strong> In an <strong>empty workspace</strong> install, it worked.  I installed a separate copy of Juno and pointed it at an empty workspace, then installed from the local feature update site. The result was that the application behaved as usual.  Although this might offer a clue, it's not a "solution" because I have too many projects that would need a lot of twiddling, and wouldn't be worth it to go this route.</p>
  
  <p><strong>Update2:</strong> 1) Did a fresh install of Juno, opened an empty workspace, closed Juno, then listed contents of <code>eclipse\configuration\org.eclipse.equinox.simpleconfigurator\bundles.info</code> and listed contents of the file system in <code>eclipse\plugins</code>.  The only difference between the two was the entries ending in <code>.source</code>, which is expected. 2) Started Juno, pointing to a copy of my Helios workspace. <code>Help &gt; Install new software... &gt; Add... &gt;  Local... &gt; (select local feature update site) &gt; (uncheck Group items by category)</code> and the rest to finish installation successfully.  3) Closed Juno and noted that only my plugin was added to <code>bundles.info</code>, and noted that only my plugin was added to the file system in <code>eclipse\plugins</code>.  In other words, each of those had one additional item which was my plugin.  4) Started Juno but the menu item from my plugin did not show, yet all indications (plugin diagnose) indicated it should work.  5) Copied the plugin jar to dropins folder, but no improvement. </p>
  
  <p>Any <strong>more</strong> guidance as to what to try next would be appreciated.</p>