Geertjan's Blog

  • May 4, 2009

run.args.extra=--branding visualvm

Geertjan Wielenga
Product Manager
Today's question of the day concerns the situation where you start a NetBeans application from the IDE, instead of from the binary launcher in the application's bin folder. Bennie Vaessen, who was at my presentation at the NL-JUG conference recently, asked about that:

I noticed that in the first part of your presentation the instance of VisualVM itself was visible, together with its corresponding icon. However, when you were developing a new plugin, and VisualVM was started from within NetBeans IDE, it was NetBeans IDE's icon that was displayed, while I was expecting to see VisualVM's icon here too, because you're developing against the VisualVM instance of the platform. What am I missing here?

Not only the icon is affected, but also the splash screen and the text in the titlebar. The way to fix this is to add this line to either platform.properties or project.properties, of the NetBeans module that you're running from the IDE:

run.args.extra=--branding visualvm

Above, the branding token is set, which specifies the branding information that should be used when the selected platform is started. What would be even better, I think, would be that when you change the NetBeans Platform for a particular module, the platform.properties or project.properties file should be automatically updated with the above key/value combination.

Anyway, simply adding the branding token of the platform you're running against, in this case VisualVM, is enough to ensure that when the module is run from the IDE, which then causes the platform to start, the correct icon, titlebar, and splash screen will be displayed.

Join the discussion

Comments ( 1 )
  • ifetayo Tuesday, May 5, 2009

    hello! i am an amateur programmer.i just want to know how i can run a program without starting my netbeans ide.e.g like a calculator appillcation

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