Did you ever be amazed when discovering a static method that provides you exactly the feature that you need?
No later than this week, I was (again) amazed by such a killer feature. It was just when I want to open the log file in an editor. With 4 classes, it was done!!
So, I will share with you these classes and some of my beloved static methods also provides by them.
- PlatformUI : the one that I used the most…
– access to the Workbench and so easy access to all parts of your application (and get the active ones),
– the PreferenceStore where you can set some preferences of the user,
– and can also create Display to… display ^^ a new window
- Platform : we can found a lot of things, I advice you take a look.
– provides a lot of OS related information,
– access to the ExtensionRegistry (all extensions declared… and providing to your extension points ;)),
– the log file location,
– … and many other things!!
- EFS (which stands for Eclipse File System) : Introduce in 3.2, I think that it is an underrated class and that it provides a good API to manipulate files.
– static access to files giving it URI, IPath, File…
– and then manipulating easily via the interface IFileStore which is returned
- IDE : A lot of convenience method to open file in editor
– convenience method to open file from inside and outside of the workspace
– convenience method to open file designed by URI, IPath, IFile,…
– convenience method to open a file at a specified Marker
– … and some other options
I let you discover all the possibilities… and share your beloved ones!!
With Eclipse 3.5, some new interesting features appears to improve the publication of Eclipse products and features.
Now you can publish p2 metadata directly from the build instead of generating it later based on binary jars.
To do that, just put this property :
You can precise repositories of metadata by setting : p2.metadata.repo and p2.artifact.repo.
An other result of setting the p2.gathering property to true is that root files contributed by features will be published into the artifact repository and associated metadata will be created. So, you have directly the feature’s root files installed.
There’s another great feature. Now you can choose the replacement of the .qualifier used in a product build. Just set the p2.product.qualifier to the qualifier you want to use.
You can now easily export source bundles too. There’s an option to generate a source bundle for each generated plug-ins.
Eclipse 3.5 provides facilities to publish features categories on export. (more info here).
This previous feature is quite useful, mostly if we look at the new software update skin!! If you have set no categories for your features, by default they won’t appeared.
You will have to checked out the “Group items by categories” options.
As we talked of the new software update skin. We can notice that the UI is greatly improved. And I found a little thing that I find useful : define names for software sites. (more info here)