X

Where did my plug-ins go?

Guest Author

The final release of NetBeans 6.1 will provide about 50 stable and well tested plug-ins on the stable and beta update centers (depending on which version of NetBeans you install, it can be more or less). However I noticed that some important plug-ins are missing. For example if you want to get the Groovy / Grails plug-ins, you won't find them in default installation. So if you want to have access to more plug-ins in your 6.1 release (or in other releases, betas, etc.), you can add a development update center to your IDE. Note that these plug-ins do not go through the same QA process as the plug-ins on the stable and beta update centers, so use this at your own risk. However the Groovy / Grails plug-ins are probably worth a little risk :)

To install the development update center to your NetBeans installation go to Tools | Plug-ins | Settings | Add update center and specify this URL:

http://deadlock.netbeans.org/hudson/job/javadoc-nbms/lastSuccessfulBuild/artifact/nbbuild/nbms/updates.xml.gz

That's it, from now on you get access to 140+ plug-ins. You can disable the daily update center easily using the checkbox if you make sure you install only tested plug-ins. In case you want to get even more plug-ins, you can also install the plug-in portal update center:

http://plugins.netbeans.org/PluginPortal/faces/PluginDetailPage.jsp?pluginid=1616

Click on "Reload catalog" to refresh the available plug-ins and you should see 300+ plug-ins being now available for you. Of course these plug-ins also vary in quality so be cautious. If this is not enough for you :) there are additional community update centers you can install. See Geertjan's blog for details.

Join the discussion

Comments ( 11 )
  • Jose Noheda Saturday, April 26, 2008

    In fact, trying to install the Groovy plug-in from there throws an error: Missing Common Scripting Language Support.


  • Roman Strobl Saturday, April 26, 2008

    Which version do you use? It works for me in the release candidate. It can't work in 6.0 or earlier... this is only for 6.1-based NetBeans.


  • xiaochong Saturday, April 26, 2008

    RC2 will throws an error: Missing Common Scripting Language Support

    RC1 work well


  • mbien Saturday, April 26, 2008

    shouldn't the plugin portal update center be pre-installed by default?

    [sidenote]

    there is a (new) validation process for each contributed plugin to the plugin portal before it is included in the update center.


  • Roman Strobl Saturday, April 26, 2008

    We're trying to include Plugin portal update center by default but it didn't happen for 6.1 yet.


  • mbien Saturday, April 26, 2008

    just checked it with rc2 and it seems like it is already included:

    http://plugins.netbeans.org/nbpluginportal/updates/6.1/catalog.xml.gz

    also in 6.0.1

    the funny thing is both xml files in the archives are empty - I never noticed this before :)

    the Plugin you mentioned installs this link:

    http://plugins.netbeans.org/nbpluginportal/files/nbms/pluginportal-update-center.xml

    (and its of course not empty)


  • Casper Tuesday, April 29, 2008

    Hmm after I added http://deadlock.netbeans.org/hudson/job/javadoc-nbms/lastSuccessfulBuild/artifact/nbbuild/nbms/updates.xml.gz and restarted, NetBeans asked to update two items. I agreed. Now I can't see any plugins anywhere, not in the "Available plugins", nor "Downloaded" nor "Installed".

    Pressing "Reload catalog" will go through all update centers, but yield no results and eventually all buttons/tabs but "Close" and "Help" are disabled.


  • Casper Tuesday, April 29, 2008

    My logfile shows:

    java.lang.NoClassDefFoundError: org/netbeans/updater/XMLUtil

    at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogParser.getDocument(AutoupdateCatalogParser.java:193)

    at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogParser.getLicenses(AutoupdateCatalogParser.java:130)

    at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogParser.getUpdateItems(AutoupdateCatalogParser.java:99)

    at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogProvider.getUpdateItems(AutoupdateCatalogProvider.java:114)

    at org.netbeans.modules.autoupdate.services.UpdateUnitFactory.appendUpdateItems(UpdateUnitFactory.java:170)

    at org.netbeans.modules.autoupdate.services.UpdateUnitFactory.getUpdateUnits(UpdateUnitFactory.java:140)

    at org.netbeans.modules.autoupdate.services.UpdateManagerImpl$Cache.<init>(UpdateManagerImpl.java:185)

    at org.netbeans.modules.autoupdate.services.UpdateManagerImpl.getCache(UpdateManagerImpl.java:161)

    at org.netbeans.modules.autoupdate.services.UpdateManagerImpl.getUpdateUnits(UpdateManagerImpl.java:90)

    at org.netbeans.api.autoupdate.UpdateManager.getUpdateUnits(UpdateManager.java:100)

    at org.netbeans.modules.autoupdate.ui.actions.AutoupdateCheckScheduler.checkUpdateElements(AutoupdateCheckScheduler.java:190)

    at org.netbeans.modules.autoupdate.ui.actions.AutoupdateCheckScheduler$5.run(AutoupdateCheckScheduler.java:169)

    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561)

    [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986)


  • cheers! Tuesday, April 29, 2008

    Just a thank you! You helped me out!

    I'd buy you a coffee, but as the old adage goes: Buy a man a starbucks, he drinks something akin to coffee, tell him to buy some fresh beans, mini grinder and an micro espresser, and he drinks real coffee for life!

    Have fun!


  • guest Wednesday, April 30, 2008

    doesn't work with 6.1 final. anyone?


  • Casper Wednesday, April 30, 2008

    Roman, are you sure the .gz should've be removed from the URL you provide? Considering the XML parsing trouble I ran into (I had to reinstall NetBeans) and the fact that http://deadlock.netbeans.org/hudson/job/javadoc-nbms/lastSuccessfulBuild/artifact/nbbuild/nbms/updates.xml looks like a perfectly fine update center feed.


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha